Publish releases from this repository - #1
Merged
Merged
Conversation
The artifacts split existed because a private source repo cannot serve the anonymous downloads Homebrew and `curl | sh` need; this repository is public, so `multiplex-cli-releases` has nothing left to do. The publish job now targets `github.repository` under GITHUB_TOKEN — the whole cross-repo RELEASE_TOKEN dance was only ever paying for that split — and takes `contents: write` on itself alone, leaving the build matrix that runs third-party toolchains read-only. v0.1.0–v0.1.2 are mirrored here byte-for-byte, so a pinned `MPX_VERSION=v0.1.1` and the `/latest` redirect both resolve from this repo today rather than from the next tag onward. The old repository keeps serving the URLs it already published. RELEASE_TOKEN stays for the tap bump, and now wants write on the tap alone.
This was referenced Aug 13, 2026
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 artifacts split existed because a private source repo cannot serve the anonymous downloads Homebrew and
curl | shneed. This repository is public, somultiplex-cli-releaseshas nothing left to do.publishnow targetsgithub.repositoryunderGITHUB_TOKEN; the cross-repoRELEASE_TOKENdance was only ever paying for the split. It takescontents: writeon itself alone, so the build matrix — the jobs running third-party toolchains over the tag's code — stays read-only.RELEASE_TOKENstays for the tap bump, and now wants write onmultiplex-term/homebrew-tapand nothing else.v0.1.0–v0.1.2 are already mirrored here byte-for-byte (verified against each release's
SHA256SUMS), so a pinnedMPX_VERSION=v0.1.1and the/latestredirect resolve from this repo today rather than from the next tag onward.v0.1.0andv0.1.1predate the public history, so their tags point at its root commit; each release says so. The old repository is untouched and keeps serving the URLs it already published.Companion PRs: homebrew-tap formula URLs and the landing repo's install script.