ci: build CPython 3.14 wheels (bump cibuildwheel to 4.x)#718
Merged
wbarnha merged 3 commits intoJul 21, 2026
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## claude/ci-confluent-driver-matrix #718 +/- ##
==================================================================
Coverage 94.81% 94.81%
==================================================================
Files 104 104
Lines 11154 11154
Branches 1202 1202
==================================================================
Hits 10576 10576
Misses 482 482
Partials 96 96 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
The release wheel job pinned pypa/cibuildwheel@v2.21.3 (Oct 2024), which predates CPython 3.14. cibuildwheel only builds the interpreters its own release knows about, so `build = "cp3*"` expanded to at most cp313 and no 3.14 wheels were ever produced or uploaded to PyPI for 0.12.0/0.12.1 -- a local install on 3.14 has to compile from the sdist (issue #715). The test matrix separately tests 3.14 via setup-python, which is why the gap only showed up in the published wheels. Bump the action to v4.1.0, which builds CPython 3.14 by default (since cibuildwheel 3.1) and still supports cp310-cp313. Because free-threading is no longer experimental in 3.14, cibuildwheel would now also build free-threaded (cp314t) wheels by default; the Cython extension has not been validated under a no-GIL interpreter, so skip `cp31?t-*` for now. Verified with `cibuildwheel --print-build-identifiers` that the linux build set is now cp310..cp314 manylinux_x86_64 (no cp314t, no musllinux). The manylinux2014 image shorthand and the existing build/skip/archs/before-build options remain valid in 4.x. Fixes #715 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HHPL4VFWQRQPpjR1gXSKyL
The redis cache backend was broken against a real server: it maps schemes to the *synchronous* redis.StrictRedis / redis.RedisCluster clients but `_get`/ `_set`/`_delete`/`connect` await them, so `await self.client.get(...)` raised "object ... can't be used in 'await' expression". It only appeared to work because every test mocks the client. * Use the asyncio clients (redis.asyncio.StrictRedis / .RedisCluster), so the awaited calls are real coroutines. Verified end-to-end against a live redis (set/get/delete round-trip). * Close the client on stop (`on_stop` -> `await client.aclose()`); the async client holds real connections. * Bind `redis = None` (not just `aredis`) on ImportError so the "not installed" guard raises ImproperlyConfigured instead of NameError. * mocked_redis fixture: patch redis.asyncio.StrictRedis (the name the backend now uses) and give the mock `aclose`. * Re-enable Test_RedisScheme / the not-installed test, asserting the async client wiring. Add a real-redis CI leg: a `test-redis-integration` job with a redis service container runs new env-gated integration tests (tests/integration/cache) that exercise the backend against a live server -- the coverage the mocks can't give. Advisory (not in the required `check` gate), matching the Kafka job. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HHPL4VFWQRQPpjR1gXSKyL
wbarnha
force-pushed
the
claude/fix-715-cibuildwheel-314
branch
from
July 21, 2026 00:02
4a2c36d to
aa75db0
Compare
wbarnha
changed the base branch from
master
to
claude/ci-confluent-driver-matrix
July 21, 2026 00:02
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.
Description
Fixes #715 — no CPython 3.14 wheels were published for 0.12.0/0.12.1, so installing on 3.14 forces a source build.
Root cause
The release
build_wheelsjob pinnedpypa/cibuildwheel@v2.21.3(Oct 2024), which predates CPython 3.14. cibuildwheel only builds the interpreters its own release knows about, sobuild = "cp3*"(inpyproject.toml) expanded to at mostcp313— nocp314wheels were ever produced, hence none uploaded to PyPI. (The test matrix tests 3.14 separately viasetup-python, which is why the gap only showed up in the published wheels, not in CI test results.)Fix
pypa/cibuildwheel@v4.1.0, which builds CPython 3.14 by default (since cibuildwheel 3.1) and still supports cp310–cp313.cp314t) wheels by default. faust's Cython extension hasn't been validated under a no-GIL interpreter, so addcp31?t-*toskip. (Comment inpyproject.tomlsays to drop it once free-threading is verified.)Verification
cibuildwheel --print-build-identifiers --platform linuxagainst the updated[tool.cibuildwheel]config:—
cp314now present,cp314tand musllinux correctly excluded. Confirmed against the cibuildwheel changelog/options that in 4.x themanylinux2014image shorthand and the existingbuild/skip/archs/before-buildoptions all remain valid, and that cp310–cp314 are still buildable.confluent-kafka-style wheel availability is not relevant here; this only changes how faust's own wheels are built.Wheels are only produced on a
release: createdevent, so this can't be exercised by PR CI — it takes effect on the next tagged release.🤖 Generated with Claude Code
Generated by Claude Code