📝 docs: use a full semver tag in the pinning example - #10
Merged
Conversation
Tags are cut as vMAJOR.MINOR.PATCH so a patch release does not move anyone already pinned. The example showed v1.0, which would have been the only tag that ever existed under that scheme.
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.
Tags are cut as
vMAJOR.MINOR.PATCH, so a patch release does not move anyone already pinned. The example showed#v1.0.Prep for the
v1.0.0tag. CI cannot run while the org is billing-locked; validated locally with./tooling/validate.sh— 5 files, exit 0.