ci(release): gate the prime release on an installable prime-sandboxes floor - #870
Merged
Merged
Conversation
… floor Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
akirillo
requested review from
DamianB-BitFlipper,
JannikSt,
JohannesHa,
burnpiro,
kcoopermiller,
kennethnym and
willccbb
as code owners
August 27, 2026 17:45
DamianB-BitFlipper
approved these changes
Aug 27, 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
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.
release-prime.ymlandrelease-sandboxes.ymlrun independently, so a push that changes both packages releases the CLI without waiting for the SDK.packages/prime/Dockerfileinstalls the CLI wheel with its dependencies resolved from PyPI, so ifprime-sandboxesis not published yet, all three image builds fail after the CLI tag, GitHub release, and PyPI upload already happened. A rerun then skips the release because the tag exists, so recovery is manual. #869 raises the floor toprime-sandboxes>=0.2.40and would be the first release to hit this.This adds an
await-sandboxes-releasejob thattag-and-releasenow needs. It reads theprime-sandboxes>=floor frompackages/prime/pyproject.tomland pollspip downloaduntil that exact version resolves, for up to 10 minutes.The gate waits on PyPI rather than on the sibling workflow's Actions status, because PyPI availability is the condition the Docker build actually needs. It also covers index propagation after that workflow finishes, and it needs no handling for the race on when the sibling run appears. A CLI-only release passes in seconds because the floor is already published. If the sandbox release fails, this job times out and the CLI is never tagged or published with an unsatisfiable floor, at the cost of a 10-minute wait before the failure surfaces.
Merge this before #869.
🤖 Generated with Claude Code