CI: Run integration tests against Kinesis with Python 3.10 - 3.14

[amotl]

About

Investigate a problem with Kinesis integration tests observed recently.

kinesis.exceptions.StreamDoesNotExist: Stream 'testdrive' does not exist

References

• Timing-related CI failures on Python 3.11, 3.13, 3.14 hampsterx/async-kinesis#56

[coderabbitai]

Warning

Rate limit exceeded

@amotl has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 4 minutes and 12 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: c08ce3d5-8808-4950-a523-7fd6e10511e6

📥 Commits

Reviewing files that changed from the base of the PR and between e65dff4 and 91d5643.

📒 Files selected for processing (2)

• .github/workflows/kinesis.yml
• pyproject.toml

Walkthrough

The GitHub Actions workflow for Kinesis CI is updated to expand the Python version test matrix from a limited set with commented entries to an explicit list of five versions: 3.10, 3.11, 3.12, 3.13, and 3.14, broadening test coverage without altering test logic or error handling.

Changes

Cohort / File(s)	Summary
Python Version Matrix Expansion .github/workflows/kinesis.yml	Expanded the python-version matrix strategy to explicitly include Python 3.10, 3.11, 3.12, 3.13, and 3.14, replacing a prior configuration with commented or limited entries.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• crate/cratedb-toolkit#606 — Also modifies .github/workflows/kinesis.yml to expand the Python version matrix for Kinesis CI.
• crate/cratedb-toolkit#609 — Modifies the same Kinesis workflow file to adjust Python versions, including re-enabling Python 3.11.
• crate/cratedb-toolkit#608 — Directly modifies the Kinesis workflow's Python version matrix configuration.

Suggested reviewers

• surister
• seut

Poem

🐰 A hop through versions, wide and far,
Python 3.10 through 3.14's star,
No more comments hiding in the shade,
Five bright versions, a grand cavalcade!
More testing, more joy—how the tests shall soar! 🌟

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly matches the main change: expanding the Python version matrix in the Kinesis workflow to run tests on Python 3.10-3.14.
Description check	✅ Passed	The description is related to the changeset, explaining the motivation (investigating Kinesis integration test failures) for running tests across multiple Python versions.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch investigate-kinesis

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[amotl]

We also had to deactivate testing against Python 3.10 with 00ac379 due to a different failure showing up. What is going on?