Repository navigation
ci: validate the release tag before publishing - #653
Merged
Merged
Conversation
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.
Publishing the v2 alpha stopped after assembly because
gh release create --fail-on-no-commitscompares the latest stable release to the repository’s default HEAD, even when a different tag is requested. The alpha tag had 338 commits absent from the stable tag.Verify that the runner checkout and the remote annotated tag both resolve to the commit prepared by the workflow. Keep
--verify-tagand the existing check that refuses to replace a published release.Validated Bash syntax and ran the tag guard against the actual alpha tag and an intentionally mismatched commit. This is a follow-up for future tagged runs; the alpha binaries and tag are unchanged.