python3.14 -m pip install confluent-kafka fails

[cclauss]

% python3.13 -m pip install confluent-kafka # is successful.
% python3.14 -m pip install confluent-kafka # fails!

https://pypi.org/project/confluent-kafka

Test results: https://github.com/cclauss/confluent-kafka-python/actions

This PR merely demonstrates that new wheels need to be published to PyPI to support Python 3.14. I am happy to close this with unmerged commits after all of its tests pass.

What

Checklist

• Contains customer facing changes? Including API/behavior changes
• Did you add sufficient unit test and/or integration test coverage for this PR?
  • If not, please explain why it is not required

References

JIRA:

Test & Review

Open questions / Follow-ups

[Copilot]

Pull Request Overview

This PR adds a GitHub Actions workflow to test pip installation of the confluent-kafka package on Python 3.14 prerelease versions across multiple operating systems.

• Adds automated testing for Python 3.14 compatibility
• Tests package installation across macOS, Ubuntu, and Windows platforms
• Enables proactive validation of package compatibility with upcoming Python releases

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[confluent-cla-assistant]

🎉 All Contributor License Agreements have been signed. Ready to merge.
✅ cclauss
_{Please push an empty commit if you would like to re-run the checks to verify CLA status for all contributors.}

[MSeal]

I'm not sure this will future proof the repo. First without building the pip install will just grab the last wheels generated rather than local changes. So the triggers shouldn't be on code changes. Second it'd be better if we actually run the test suite against the compiled binaries in semaphore.yml. Checking for wheel viability should probably be an additional job triggered therein for new versions, running the while suite on every combination of os and python version is probably too much overhead for PRs.

[cclauss]

Sorry. semaphore.yml is completely opaque to me, so I have no idea how to modify it to generate Python 3.14 wheels.

This PR merely demonstrates that new wheels need to be published to PyPI to support Python 3.14. I am happy to close this with unmerged commits after all of its tests pass.

Python v3.14 -- October 7th

• https://www.python.org/download/pre-releases
• https://www.python.org/downloads/release/python-3140rc2 (rc3 is scheduled to be released today)

Call to action
We strongly encourage maintainers of third-party Python projects to prepare their projects for 3.14 during this phase, and publish Python 3.14 wheels on PyPI to be ready for the final release of 3.14.0, and to help other projects do their own testing. Any binary wheels built against Python 3.14.0 release candidates will work with future versions of Python 3.14.