Repository navigation
Changeset to cut v3.9.4 - #3610
Merged
Merged
Conversation
v3.9.3 was versioned but its publish failed at the build, so nothing shipped. A cli patch bump gives the release workflow a version to cut. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Adds a patch changeset for
@prosopo/cli, so the release workflow has something to version.Why
v3.9.3 was versioned and tagged, but its publish failed at the build step (fixed in #3609), so nothing was published. Re-running the release workflow then failed because the only pending changeset was empty, which left nothing to commit. This bump produces v3.9.4, which ships #3602.
Testing
Changeset only.
🤖 Generated with Claude Code