CI: bump uv to 0.11.26 so Python 3.14 builds use stable CPython#681
Merged
Conversation
uv 0.7.5 predates the stable CPython 3.14.0 release, so `uv python install 3.14` resolved to the newest 3.14 in its bundled python-build-standalone list: 3.14.0a6. The torch 2.11 cp314 wheel is built against the stable 3.14 ABI, and importing it on the alpha interpreter segfaults, which get_torch.cmake reports as "Failed to import PyTorch". This broke both Python 3.14 variants of publish.yml on release/v0.5 and nightly-publish.yml on main. uv 0.11.26 resolves 3.14 to stable CPython 3.14.6. The pinned setup-uv action (v5.4.2) downloads the requested uv version by URL and skips checksum validation for versions it does not know, so no workflow changes are needed. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Signed-off-by: Jonathan Swartz <jonathan@jswartz.info>
swahtz
force-pushed
the
fix/ci-uv-python314
branch
from
45d21ce to
8404d62
Compare
harrism
approved these changes
Jul 2, 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.
Problem
Both Python 3.14 variants of
publish.ymlfail onrelease/v0.5(run 28566079399), and the same two jobs fail innightly-publish.ymlonmain(run 28433783911). The 3.14 lane has never built successfully since it was added in #573.The CMake error is misleading:
Root cause
.github/versions.jsonpins uv 0.7.5 (May 2025), which predates the stable CPython 3.14.0 release. Its bundled python-build-standalone list tops out at the March 2025 alpha, so the build jobs install a pre-release interpreter:The torch 2.11
cp314wheel installs fine (the alpha reports thecp314tag) but is compiled against the stable 3.14 ABI, which CPython alphas don't guarantee — soimport torchsegfaults inside theget_torch.cmakeprobe. Python 3.10–3.13 are unaffected because uv 0.7.5 knows stable builds of those series.Fix
Bump
uv.versionto 0.11.26. Verified locally that it resolves3.14to stable CPython 3.14.6. No workflow changes needed: the pinnedsetup-uvaction (v5.4.2) installs whatever uv version is requested, downloading by URL and skipping checksum validation for versions not in its manifest.Side effect: newer patch releases of 3.10–3.13 will also be picked up.
After merge
This needs to be cherry-picked to
mainper the burndown process — nightly-publish there hits the same failure.🤖 Generated with Claude Code