docs: describe the tap deploy key instead of the retired PAT - #103
Open
ernestoongaro wants to merge 1 commit into
Open
ernestoongaro wants to merge 1 commit into
ernestoongaro wants to merge 1 commit into
Conversation
The release prerequisites still told readers to set HOMEBREW_TAP_GITHUB_TOKEN with contents:write on the tap. That secret was replaced in #102 by an ed25519 deploy key scoped to the tap alone. Also record the protect-main ruleset, since the deploy-key bypass is what keeps the release workflow able to push to main while everyone else goes through a pull request. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
The release prerequisites in
DEVELOPMENT.mdstill told readers to setHOMEBREW_TAP_GITHUB_TOKENwithcontents:writeon the tap. #102 replaced that secret with an ed25519 deploy key scoped to the tap alone, so the instructions pointed at a credential the workflow no longer reads.Also records the
protect-mainruleset on the tap, now enforcing: the deploy-key bypass is what keeps the release workflow able to push tomainwhile every other actor goes through a pull request.Docs only — no workflow or code changes.
🤖 Generated with Claude Code