8000 fix(release): skip Homebrew cask upload when tap token is unset by adeelahmad · Pull Request #6 · adeelahmad/Tether · GitHub
[go: up one dir, main page]

Skip to content

fix(release): skip Homebrew cask upload when tap token is unset - #6

Merged
adeelahmad merged 1 commit into
mainfrom
claude/release-homebrew-szp227
Oct 11, 2026
Merged

adeelahmad merged 1 commit into
mainfrom
claude/release-homebrew-szp227

Conversation

@adeelahmad
Copy link
Copy Markdown
Owner

Requested by Adeel · project thread

What

A tagged release no longer fails when the HOMEBREW_TAP_GITHUB_TOKEN secret (or the adeelahmad/homebrew-tap repo) is missing. The cask is still rendered into dist/, but its upload is skipped and the rest of the release ships.

Why

skip_upload: auto only skips prereleases, so a stable tag tried to push the cask with an empty token and failed, even though the workflow comment said the tap update would be skipped.

How tested

skip_upload is now templated: true when the token is empty, auto otherwise. Validated with GoReleaser v2 locally (goreleaser check, plus a non-snapshot release against a throwaway local tag with GitHub release publishing disabled):

  • token empty → homebrew cask: pipe skipped … reason=brew.skip_upload is set

  • token set → falls through to auto behaviour as before

  • Release config only; no Go code changed

  • make test-integration (n/a)

Security

  • No new way to reach the browser without auth, and nothing new is logged that could hold a cookie or token.

🤖 Generated with Claude Code

https://claude.ai/code/session_012hxxLWW2T83zxJLY5Ha1MY


Generated by Claude Code

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012hxxLWW2T83zxJLY5Ha1MY
@adeelahmad adeelahmad self-assigned this Oct 11, 2026
@adeelahmad
adeelahmad merged commit 07e10d3 into main Oct 11, 2026
13 checks passed
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.

2 participants

0