ci: modernize Tests & Publish via cibuildwheel (Python 3.11–3.14) - #519
Merged
Conversation
4 tasks
youben11
approved these changes
Jul 26, 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
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.
Summary
Modernize the Tests and Publish CI so they build, test, and ship on the current GitHub runner images and cover Python 3.11–3.14.
The macOS/Windows failures on the newer runners came from their default CMake 4.x rejecting the vendored protobuf/json's pre-3.5
cmake_minimum_required(plus a latent Windows protobuf-install bug), not from the dependencies themselves. This keeps those deps as-is and lets the runners' built-in CMake accept them viaCMAKE_POLICY_VERSION_MINIMUM=3.5.Changes
fdopenclash.ubuntu-24.04/windows-2022/macos-14: build cp311–cp314, run the test suite on the latest (cp314) only.publish_wheels.ymlto the same recipe (cp311–cp314), so shipped wheels are produced exactly like the tested ones.--config Releasefor the Windows build/install (newer CMake rejects an empty--config).workflow_dispatchonly, it's broken and fixed separately; this stops it reding every PR.Notes
macos-14); the retiredmacos-13Intel target is dropped.Next steps (follow-ups, not in this PR)
black==22.3.0can't run on 3.14 (it crashes onasyncio.get_event_loop()). Bumping to a 3.14-compatible black also reformats ~17 files, so do it as its own PR (bump black + reformat + updatepyproject.tomltarget-version).workflow_dispatch-only. Restore it in a dedicated PR; itsdeps.bzl/BUILDfiles still pin the old SEAL and-std=c++17.CMAKE_POLICY_VERSION_MINIMUM=3.5is a transitional escape hatch for the old protobuf/json floors. The durable fix is moving to a newer protobuf (which needs a FetchContent-targets integration), after which the shim can be dropped.windows-2022,macos-14, and Xcode 15.4. When those retire, the deferred toolchain modernization applies (e.g., xtensor 0.27 + C++20 to build under AppleClang 17 onmacos-15).