docs: record that release tag names cannot be reused - #39
Merged
Conversation
Immutable releases burn a tag name when a release publishes under it, so v0.0.6 could not be recreated after its release was deleted. Skipping to 0.0.7. Release-As: 0.0.7
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.
v0.0.6cannot be released. Immutable releases are enabled on this repo, so a tag name is burned the moment a release publishes under it — deleting the release and the tag does not give the name back. release-please failed on #37 withtag_name was used by an immutable release, and it will keep failing on every push to main until the version moves.v0.05andv3.0.0are spent the same way.Tag creation itself is fine — I created and deleted a probe tag to rule out a ruleset, so there is nothing for an admin to change.
#37 is relabelled
autorelease: taggedso release-please stops retrying 0.0.6, and the footer below moves the next release to 0.0.7. npm goes 0.0.5 → 0.0.7; 0.0.6 never appears there.Please squash-merge without editing the commit message — release-please reads the
Release-As:footer off the commit that lands on main, and dropping it means no release PR opens.Release-As: 0.0.7