Repository navigation
ci: let release rehearsals pass on an already published version - #634
Merged
Merged
Conversation
Tag runs check that the version is not already on npm.
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.
The first manual rehearsal of the release workflow on
mainfailed at its last step: run 41269166106. npm 11'snpm publish --dry-runasks the registry, which refuses a version that is already published ("You cannot publish over the previously published versions: 4.3.0"). So every rehearsal from a branch would fail, though the real tag would pass.npm pack --dry-run. It lists the same files without contacting the registry.Rehearsed on this branch: run 41269331940.
verifypassed with the 8-file tarball, andpublishwas skipped.🤖 Generated with Claude Code