ci: skip publish when the tagged version is already on npm#44
Merged
Conversation
So a retroactive tag (e.g. v0.1.0 for the already-published release) or any re-tag no-ops cleanly instead of failing on a duplicate publish.
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 release workflow runs
npm publishon anyv*tag. A retroactive tag (e.g.v0.1.0for the already-published release) or any accidental re-tag would fail on a duplicate publish.This adds a guard step that checks
npm view tweakit@<version>first and skips the publish when that version is already on the registry — so re-tagging no-ops cleanly instead of going red. New versions publish exactly as before.