Repository navigation
fix(release): tag a version npm rejects as already published - #1378
Merged
Merged
Conversation
npm view can return a stale miss for a package created minutes earlier, so a version published out of band reached npm publish and failed the release with E403. Treat that rejection as already published and only tag it.
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 17 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Maple reviewNothing to review The only changed file is
|
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
1 participant
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 changesets Release run failed:
@maple-dev/alchemy@0.2.0was published by hand minutes earlier (first-publish bootstrap),npm viewserved a stale miss for the brand-new package, andnpm publishthen failed with E403 "cannot publish over the previously published versions".This treats that specific rejection as already published: the script logs it and tags/releases the version instead of failing. Any other publish error still fails the run.
🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.