chore(release): publish the formula to the klarlabs-studio tap#158
Merged
Conversation
tokenops is a klarlabs-studio repo and HOMEBREW_TAP_TOKEN is a klarlabs-studio org secret, but the formula was pointed at felixgeelhaar/homebrew-tap — a personal repo the org secret cannot reach. briefkasten hit that combination first: its v0.31.0 published all 22 signed artifacts and then failed on the brew step with "403 Resource not accessible by personal access token". Note for whoever merges: tokenops.rb exists only in the personal tap, so the first release after this lands creates it in the org tap and the old copy stops being updated. A tap_migrations.json entry in the personal tap carries those users over, but it has to come AFTER that release — a redirect to a tap that does not yet hold the formula breaks the install it was meant to preserve. Claude-Session: https://claude.ai/code/session_01BFsL9VmX5KHW8cnLMRPei3
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.
Why
tokenops is a
klarlabs-studiorepo andHOMEBREW_TAP_TOKENis aklarlabs-studioorg secret — but the formula was pointed atfelixgeelhaar/homebrew-tap, a personal repo that secret cannot reach.briefkasten hit that combination first: v0.31.0 published all 22 signed artifacts and then failed on the brew step with
A
403rather than a401is the fine-grained-PAT signature — it authenticated, but the target repo is outside its scope. The comment above the block asserted the token hadcontents:writeon the personal tap; it does not, and after this change it does not need to.Sequencing note for whoever merges
tokenops.rbexists only in the personal tap. So the first release after this lands creates it in the org tap, and the personal-tap copy stops being updated — anyone installed fromfelixgeelhaar/tapsilently pins to their current version.A
tap_migrations.jsonentry in the personal tap ({"tokenops": "klarlabs-studio/tap"}) carries them over, but it has to come after that first release: a redirect pointing at a tap that does not yet hold the formula breaks the very install it exists to preserve. Neither tap contains that file today.Note for a follow-up
goreleaser checkreports the config "uses deprecated properties" —brews:was deprecated in GoReleaser v2.16 in favour ofhomebrew_casks:, which is also Homebrew's guidance for a pre-compiled binary. That predates this PR and is left alone to keep the change to one line of intent.https://claude.ai/code/session_01BFsL9VmX5KHW8cnLMRPei3