Repository navigation
Let tag currency tell a release from a moving tag - #74
Merged
Merged
Conversation
A package with more than one v* tag cuts real releases, and a published release must not be moved. The check told those packages to force-move it, and went red on every Dependabot bump, since a .github-only commit put the release behind main. console's scheduled hygiene was red for exactly that. For released packages, commits that touch only .github/ now pass, and unreleased shipped code asks for the next patch release instead of a moved tag. Moving-tag packages are unchanged. Pinned by a test against a stub gh.
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
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.
A package with more than one v* tag cuts real releases, and a published
release must not be moved. The check told those packages to force-move it,
and went red on every Dependabot bump, since a .github-only commit put the
release behind main. console's scheduled hygiene was red for exactly that.
For released packages, commits that touch only .github/ now pass, and
unreleased shipped code asks for the next patch release instead of a
moved tag. Moving-tag packages are unchanged. Pinned by a test against a
stub gh.