Release - Wait for crates.io publish propagation#5352
Merged
Conversation
bfops
reviewed
Jun 16, 2026
clockwork-labs-bot
requested review from
cloutiertyler and
jdetter
as code owners
bfops
reviewed
Jun 16, 2026
bfops
reviewed
Jun 16, 2026
…er' into bot/split-public-release
…lit-public-release' into bot/release-crates-wait
bfops
changed the title
jdetter
reviewed
Jul 1, 2026
jdetter
approved these changes
Jul 1, 2026
jdetter
left a comment
jdetter
left a comment
Contributor
There was a problem hiding this comment.
LGTM - I have not manually tested this one.
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
3 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.
Description of Changes
Stacked on #5325.
This updates the crates.io release target so after each crate publish succeeds, or is detected as already published, the release tool waits until
cargo info <crate>@<version>can resolve that exact version from the registry before continuing to later crates.This prevents dependent crates from being published before crates.io has indexed the just-published dependency version.
API and ABI breaking changes
None.
Expected complexity level and risk
Testing
Unsure how to test without a release.