ci: pin ant sidecar via .ant-version — stop floating to latest ant-client (V2-760) - #186
Merged
Conversation
…ient (V2-760) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Jul 24, 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.
Found during RC wave V2-759: on the tag-push path,
release.yml'sresolve-ant-versionjob fell back togh release list --repo WithAutonomi/ant-client --limit 1— i.e. whatever ant-client release is latest at build time. That's a race (an ant-client release landing mid-wave changes the shipped sidecar away from the wave's pinned ant-core) and makes tag re-builds non-reproducible. v0.9.4-rc.1 was safe only by coincidence (latest was the wave target).Changes:
.ant-versionfile pinning the sidecar (ant-cli-v0.3.1— what v0.9.4-rc.1 actually shipped). The pin now travels with the tag, and RC waves bump it like any other pin (one more line in theclaude/rc-bump-*PR).resolve-ant-versionpriority is now dispatch input >.ant-version; if both are absent it errors instead of silently floating. Thegh release listfallback (and its now-unusedGH_TOKEN) are gone.Follow-up (separate PR, after this merges):
release-graph.tomlin release-ops gains a real pin site + regex for this edge, replacing itsinformationalmarker.🤖 Generated with Claude Code