Increase the timeout for crates.io publishes#19287
Merged
zanieb merged 3 commits intoastral-sh:mainfrom May 5, 2026
Merged
Conversation
The default 60s wait for uploaded crates to appear in the crates.io index has been exceeded during workspace publishes, leaving the run with dozens of unpublished dependents. The `publish.timeout` config key is gated behind nightly's `-Zpublish-timeout`, so install the nightly toolchain just for this job and pass the flag with a 600s timeout.
zsol
approved these changes
May 5, 2026
Member
zsol
left a comment
There was a problem hiding this comment.
This seems fine, I wonder if we should limit the blast radius of the crates publishing. For example by moving it to the end of the workflow, or marking it optional
Member
Author
|
For that, see #19291 |
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
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.
rust-lang/cargo#11222