Repository navigation
ci: install uv and maturin from PyPI when GitHub release downloads fail - #1372
Merged
Merged
Conversation
A local setup-uv action installs the pinned uv from PyPI instead of GitHub releases. Each maturin-action step retries once, and macOS, Windows and source distribution builds then fall back to the same maturin from PyPI.
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.
Why
Since about 09:00 UTC, CI jobs fail in setup because GitHub release downloads return 504 errors or error pages.
astral-sh/setup-uvdownloads uv from GitHub releases, andPyO3/maturin-actiondownloads maturin from them. No repository code runs in those jobs, so every pull request is blocked. PyPI is not affected.Changes
setup-uvaction replacesastral-sh/setup-uvin every workflow. It installs the same pinned uv (0.12.3) from PyPI using the runner's cached Python 3.12, leaves that Python offPATH, and keeps the uv cache keyed on the same dependency files. Unlike the old action, it doesn't prune the cache before saving.maturin-actionstep inbuild-distributions.ymlnow tries once more if it fails. If the wheel builds on macOS and Windows and the source distributions fail twice, they build with maturin 1.16.0 from PyPI, the version the action resolves for this repository, using the same arguments and environment. Linux wheels need the action's manylinux container, so they only get the retry.Verification
make check-ci.PATH, andscripts/maturin_from_pypi.sh sdistbuilds the sqb source distribution with maturin 1.16.0 from PyPI.