Repository navigation
chore: run on Python 3.15 - #111
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Align Python versions .python-version, .github/workflows/ci.yml, Dockerfile |
The version file, CI lint and test jobs, and Docker base image now specify Python 3.15 instead of Python 3.14. |
Estimated code review effort: 1 (Trivial) | ~4 minutes
Change: Other
Merge Risk: 
Minimal · up to 38f84
-
The Python 3.15 configuration changes are consistent across the version file, CI, and Docker configuration.
Pre-merge checks: 
5
-
Full details: Docstring Coverage
-
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (3 skipped: 3 unsupported.)
-
Finishing Touches
-
Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
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.
A rabbit checks the version pin,
Python three-fifteen hops in.
CI runs lint and tests anew,
The Docker base updates too.
One neat upgrade, line by line,
Says the rabbit: “All looks fine!”
Python 3.15 is the current release. This moves the runtime (CI,
.python-version, Docker where present) to 3.15.requires-python, rufftarget-versionand mypypython_versionstay at 3.14 as the supported floor.🤖 Generated with Claude Code