Build wheels in manylinux_2_28 containers#7
Merged
Conversation
20d27fe to
ce41af0
Compare
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.
This switches wheel builds to the official
quay.io/pypa/manylinux_2_28_x86_64image so the backend package is built against a realglibc 2.28baseline instead of inheriting a newer Ubuntu runtime. The release, wheel, and Rust quality workflows now share the same manylinux builder, and the container bootstrap path installs the CUDA 12.9 toolkit and other build dependencies at runtime.This replaces the earlier
manylinux_2_39stopgap with the compatibility target we actually want for public Linux wheels. It also keeps the localtools/run_in_container.shpath aligned with CI so the release artifact and developer validation use the same build contract.