Problem
Release job
Published uv-build v0.11.16 at registry `crates-io`
error: no packages ready to publish but 25 packages remain in plan with 1 awaiting confirmation: uv v0.11.16, uv-audit v0.0.49, uv-bin-install v0.0.49, uv-build-frontend v0.0.49, uv-cache v0.0.49, uv-cli v0.0.49, uv-client v0.0.49, uv-configuration v0.0.49, uv-dispatch v0.0.49, uv-distribution v0.0.49, uv-extract v0.0.49, uv-installer v0.0.49, uv-publish v0.0.49, uv-python v0.0.49, uv-requirements v0.0.49, uv-requirements-txt v0.0.49, uv-resolver v0.0.49, uv-scripts v0.0.49, uv-settings v0.0.49, uv-test v0.0.49, uv-tool v0.0.49, uv-torch v0.0.49, uv-types v0.0.49, uv-virtualenv v0.0.49, and uv-workspace v0.0.49
note: this is an unexpected cargo internal error
note: we would appreciate a bug report: https://github.com/rust-lang/cargo/issues/
note: cargo 1.97.0-nightly (eb94155a9 2026-04-09)
Publishing workspace crate versions that do not exist on crates.io:
uv@0.11.16
uv-audit@0.0.49
Is this merely a crates.io service timeout with unclear error, different presentation than other times?
Should / can uv request crates.io credentials that allow more uploads from a runner at once?
Other failures — likely just timeouts
Notably 0.11.9 (mentioned) release job also recently failed, but logs more clearly report upload timeouts.
= note: the registry may have a backlog that is delaying making the crate available. The crate should be available soon.
error: unable to publish uv v0.11.9, uv-audit v0.0.42, uv-bin-install v0.0.42, uv-build-frontend v0.0.42, uv-cache v0.0.42, uv-cli v0.0.42, uv-client v0.0.42, uv-configuration v0.0.42, uv-dispatch v0.0.42, uv-distribution v0.0.42, uv-distribution-types v0.0.42, uv-extract v0.0.42, uv-git v0.0.42, uv-installer v0.0.42, uv-publish v0.0.42, uv-python v0.0.42, uv-requirements v0.0.42, uv-requirements-txt v0.0.42, uv-resolver v0.0.42, uv-scripts v0.0.42, uv-settings v0.0.42, uv-test v0.0.42, uv-tool v0.0.42, uv-torch v0.0.42, uv-types v0.0.42, uv-virtualenv v0.0.42, and uv-workspace v0.0.42 due to a timeout while waiting for published dependencies to be available.
Steps
No response
Possible Solution(s)
No response
Notes
No response
Version
Github runner, `cargo 1.97.0-nightly (eb94155a9 2026-04-09)`
https://github.com/astral-sh/uv/actions/runs/26253837281/workflow
Problem
Release job
Is this merely a crates.io service timeout with unclear error, different presentation than other times?
Should / can uv request crates.io credentials that allow more uploads from a runner at once?
Other failures — likely just timeouts
Notably
0.11.9(mentioned) release job also recently failed, but logs more clearly report upload timeouts.Steps
No response
Possible Solution(s)
No response
Notes
No response
Version