ci: Use GITHUB_TOKEN for homebrew tap automation instead of PAT#26
Open
ci: Use GITHUB_TOKEN for homebrew tap automation instead of PAT#26
Conversation
- Removes need for custom PAT secret - Uses built-in GITHUB_TOKEN which works for same-org repos - More secure and compliant approach
84344e4 to
ab32e43
Compare
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.
Changes
HOMEBREW_TAP_TOKENwith built-inGITHUB_TOKENin release workflowBenefits
✅ Security: Uses GitHub's built-in token instead of custom PAT
✅ Compliance: No need to manage additional secrets
✅ Maintenance: One less token to rotate/manage
Testing
The automation will be tested on the next version release. The homebrew tap repository is already configured to handle the repository dispatch events from this workflow.
Related
brew tap actual-software/tap && brew install rulectl