Merged
Conversation
The CHECKOUT_REF workaround could build from a commit different than what the tag should represent. Reverting to the original tag-based checkout. The tag ruleset needs a bypass for the repo owner to allow tag pushes that trigger the release workflow.
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.
Summary
CHECKOUT_REFworkaround from Fix release workflow checkout for workflow_dispatch #119Why
The workaround checked out
mainforworkflow_dispatch, which could build code ahead of the intended release point. Tags should be immutable snapshots — the correct fix is to add a repo owner bypass on the tag creation ruleset, then push tags normally.After merging
Add a bypass for Repository admin (or your user) on the tag ruleset:
Settings > Rules > Rulesets > edit the rule restricting tag creation > add bypass