feat(codex): release wiring for codex-on-event (M4)#169
Merged
Conversation
Add a codex-on-event build block to .goreleaser.yaml (CGO off,
linux/darwin × amd64/arm64, version ldflags), so tagged releases publish
codex-on-event-{os}-{arch} binaries + checksums alongside the Claude Code
and Cursor binaries. Wire scripts/release.sh to bump the pinned VERSION in
scripts/codex-on-event.sh in lockstep, and document it in DEVELOPMENT.md.
The bootstrap download/verify logic already exists (M3); its VERSION stays
at the 0.0.0 placeholder until the next release, when release.sh bumps it
in the same commit that first publishes codex binaries — so the pin and
the published assets stay consistent.
SIG-172
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
bertschneider
approved these changes
Jul 14, 2026
bertschneider
left a comment
bertschneider
left a comment
Member
There was a problem hiding this comment.
Looks good 👍
Similar to the other ticket, I wonder if we could improve the release process, e.g. using the pushed git tag to automatically set the plugin version or the like. But out of scope for this PR.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Wires the
codex-on-eventbinary into the release pipeline so tagged releases publish it alongside the Claude Code and Cursor binaries. Closes the M4 gap (SIG-172).What
.goreleaser.yaml— adds acodex-on-eventbuild block (CGO off, linux/darwin × amd64/arm64, version ldflags), mirroringcursor-on-event. Tagged releases now publishcodex-on-event-{os}-{arch}binaries and include them inchecksums.txt.scripts/release.sh— bumps the pinnedVERSIONinscripts/codex-on-event.shin lockstep with the other bootstrap scripts + plugin manifests.DEVELOPMENT.md— documents the codexVERSIONline and thatrelease.shupdates all of them in one commit.The bootstrap download/verify logic already exists (M3). Its
VERSIONstays at the0.0.0placeholder until the next release —release.shbumps it in the same commit that first publishes codex binaries, so the pin and the published assets stay consistent. (No release is cut here; codex install isn't GA until M6.)Testing
Verified locally with a goreleaser snapshot (no publish):
goreleaser check— config valid.goreleaser release --snapshot --clean— produces all 4codex-on-event-{darwin,linux}-{amd64,arm64}binaries, andchecksums.txtincludes all 4. Behaves identically to the existing two builds.The
"artifact already present"snapshot warning is pre-existing and benign — it fires for all three builds (on-event,cursor-on-event,codex-on-event) and current releases ship with it.The download → checksum-verify → exec → OTLP path is already exercised in CI by #166's install contracts (Contract G/H) against a locally-staged binary; the literal GitHub download will be validated end-to-end at the first codex-containing release.
SIG-172