Skip to content

fix: verify tap write authentication before release - #401

Merged
TheWeiHu merged 1 commit into
mainfrom
fix-tap-release-auth
Sep 17, 2026
Merged

TheWeiHu merged 1 commit into
mainfrom
fix-tap-release-auth

Conversation

@TheWeiHu

Copy link
Copy Markdown
Owner

The release preflight accepted the repository owner's API permissions even when the fine-grained token could not push, leaving published binaries without a Homebrew update. Verify Git write authentication with a dry-run push before publishing, and pass the token through askpass rather than embedding it in Git arguments.

Add a manual recovery run for an existing release: download its checksums, publish its formula, then run the macOS Homebrew canary. Recovery does not rebuild or upload release assets. Checkout credentials are not retained.

Validation: full make test; regression cases for denied write access and unchanged formulas; shell syntax and workflow YAML checks; real dry-run tap authentication with existing local credentials. Live recovery of v1.5.29 will verify the repository secret and Homebrew install after merge.

@TheWeiHu
TheWeiHu merged commit 6a2460a into main Sep 17, 2026
3 checks passed
@TheWeiHu
TheWeiHu deleted the fix-tap-release-auth branch September 17, 2026 19:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant