release(0201): auto-advance the stable channel ref on each cut (Model B plumbing)#357
Merged
Conversation
The marketplace stable entry now pins source.ref=stable (a moving branch in this repo) instead of a per-release tag, so publishing to the stable channel is advancing that branch — no longer a hand-edit of the spacedock-dev/marketplace repo. The stamp step, after pushing the stamped release commit to main, fast-forwards refs/heads/stable to it (GITHUB_TOKEN suffices — same repo). Restructured the no-op-stamp branch so the stable advance always runs. Guard parser: skip refspec pushes (target contains ':') so the stable push does not shadow the bare-branch stamp target. New TestStampStepAdvancesStableRef locks the stable-advance push (without it the stable channel would freeze at the prior release, since the marketplace manifest is now static). Whole-repo go test ./... green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Makes the stable marketplace channel a moving
stableref the release advances automatically, so the standalonespacedock-dev/marketplacemanifest never needs a per-release hand-edit again.Already landed (one-time, no behavior change)
stablebranch in this repo at the v0.20.0 commit (= exactly what the stable entry served viaref: v0.20.0).spacedock-dev/marketplacestable entrysource.ref:v0.20.0→stable. The manifest is now static.This PR
release.ymlstamp step, after pushing the stamped release commit tomain, also fast-forwardsrefs/heads/stableto it (GITHUB_TOKENsuffices — same repo, unlike the cross-repo homebrew-tap push). Restructured the no-op-stamp branch so the stable advance always runs.:) so the stable push does not shadow the bare-branch stamp target.TestStampStepAdvancesStableReflocks the stable-advance push (adversarially verified: removing the push reds it). Without it the stable channel would freeze at the prior release, since the manifest is now static.The host keys re-pull on the source refs plugin.json version (not the marketplace entry version), so when
stableadvances to a stamped release commit the host sees the version bump and re-pulls. Whole-repogo test ./...green. Replaces the manual post-cut marketplace repoint with release-machinery (theezn/stamp-then-tag lane, design (b)).🤖 Generated with Claude Code