Two-channel release (stable→main / edge spacedock@next→next) + per-channel devBranch stamp + next-publish#339
Merged
Conversation
…p swap Make each released spacedock channel auto-install its own channel's plugin: the stable binary (devBranch=main) installs the `main` plugin, the edge binary (devBranch=next) installs the `next` plugin. The single mechanism is the build-time devBranch ldflag, set per channel by two goreleaser builds. .goreleaser.yaml: replace the single devBranch=next build with two builds (spacedock-stable → main, spacedock-edge → next), two archives (edge carries an `_edge` asset suffix), and two homebrew_casks (stable `spacedock`, edge `spacedock@next`), each cask pinning only its channel's archive via `ids:`. One `goreleaser release --snapshot` emits both channels; the built stable/edge binaries' fresh-HOME front-door auto-install was observed issuing `marketplace add …@main` / `…@next` (claude) and `--ref main` / `--ref next` (codex) — AC-a, AC-c, AC-d live smoke. release.yml: single-target swap of the "Stamp plugin manifests" step next→main (release.yml is tag-only-triggered → exactly one stamp target, the stable channel, whose plugin lives on `main`). Not a per-channel branch. internal/release/channel_agreement_guard_test.go: NEW green guard asserting the binary-side pair agreement — release.yml stamp target == .goreleaser.yaml stable devBranch, both `main` — parsed from two independently-authored artifacts. The full tri-surface ==main check (adding marketplace.json ref) is skipped until pj flips the ref; structured so pj extends it green-by-construction at the flip. internal/cli/codex_channel_smoke_test.go: hermetic per-channel front-door tests driving runClaude/runCodex no-plugin auto-install with devBranch set per channel, observing the channel-correct @ref / --ref in the recorded install seam — AC-a/d. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
clkao
added a commit
that referenced
this pull request
Jun 9, 2026
clkao
added a commit
that referenced
this pull request
Jun 9, 2026
clkao
added a commit
that referenced
this pull request
Jun 9, 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.
Ahead of the 0.20.0 flip, each released channel's binary must install its own channel's plugin — this stamps
devBranchper channel and emits both casks.What changed
devBranchper channel via two goreleaser builds (stable→main, edge→next).spacedockand edgespacedock@next, each pinning its own archive.release.ymlplugin-manifest stamp step tomain(single-target, tag-only trigger).internal/releaseguard pinning the binary-side pair agreement onmain.--ref main/--ref nextinstall argv.Evidence
goreleaser release --snapshotemits both casks (distinct archives/shas); built binaries install@main/@next(claude) and--ref main/next(codex), observed in argv.go test ./internal/release/ ./internal/cli/→ 75 + 341 passed; detached adversarial audit caught every weakening, no material findings.Review guidance
k6d