Repository navigation
fix(ci): qualify Python runners for wheel and release checks - #43
Merged
Merged
Conversation
Merged
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.
The moving Ubuntu runner caused two Python compatibility failures: Python 3.9 wheel tests could not find a runtime on Ubuntu 26.04, and Release-plz semver checks selected Python 3.14 even though PyO3 0.23 supports through 3.13.
Pin the wheel-test job to Ubuntu 24.04 while retaining all five Python versions (3.9–3.13). Also qualify the Release-plz environment with Ubuntu 24.04, explicit Python 3.12 and PYO3_PYTHON=python. Semver checks, feature coverage, release permissions and downstream job conditions remain enabled.
Validation: the original Python 3.9 failure and Release-plz failure on base 22d344a are retained. An isolated check on that exact base reproduced the PyO3 refusal with Python 3.14 (exit 101); the identical command with Python 3.12 passed. The probe was
PYO3_PYTHON=<interpreter> cargo check --locked --lib --features python; it isolates the library build prerequisite and does not claim a complete release run. Both HOME guards were clean. All 11 existing crate-dispatch controls passed under the guard.The earlier head completed all 13 hosted checks. Fresh hosted CI is required for this expanded two-workflow correction. Normal non-author review and base admission remain required before landing.
Bead: aegis-sg3
Overlap preflight: a75c7e0b9bd81b306de321871f88c19b20358d8d9f6a43cddd0c63ec0d727928