Repository navigation
ci: re-running the release publishes the latest tag if npm lacks it - #4
Merged
Merged
Conversation
When sem made no new release, the publish step was skipped, so a publish that failed (v0.1.1 and v0.1.2, before the package existed on npm) could never be retried. With no new release, the job now takes the latest v* tag, publishes it from that tag if npm doesn't have it, and still skips versions npm already has.
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.
Re-running NPM release after a failed publish did nothing.
semsaw the tag already existed, so there was no new release, and Publish to npm was skipped. v0.1.1 and v0.1.2 both failed to publish (the package isn't on npm yet) and couldn't be retried.Now, when there's no new release, the job takes the latest
v*tag. It publishes that tag's code if npm doesn't have the version, and skips it if npm already does.This is
ci:, so no release. Merging re-runs the workflow onmain, which tries v0.1.2 again.