Repository navigation
ci(release): require tags on main and scope the tap token to releases - #4
Merged
Merged
Conversation
Reject release tags whose commit is not on main, run the tap job in the homebrew-tap environment that only admits v*.*.* tags, and refuse to replace a newer formula with an older one.
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.
Summary
main(same check as quota-bar and whisper).tapjob in the newhomebrew-tapenvironment, which only admitsv*.*.*tags.Formula/gbat.rbwith an older version (same guard as ferry).Follow-up outside this PR
HOMEBREW_TAP_TOKENis still a repository secret, which the job keeps reading until the same secret exists in thehomebrew-tapenvironment. After setting it there, delete the repository-level copy.