Relax Python version constraints from <3.13 to <3.14

[accelazh]

Thanks InectGit! I have tried out the plugin with my Python version 3.13.8. It works like a charm. Here to relax the version constraint in pyproject.toml for Python, from <3.13 to <3.14.

Summary by CodeRabbit

• Chores
  • Expanded official Python compatibility to include Python 3.13.
  • Users on Python 3.13 can now install and run the package without version pinning issues.
  • No changes to features or behavior; existing environments on Python 3.11–3.12 remain fully supported.
  • Dependency set unchanged; no migration steps required.

[gemini-code-assist]

Summary of Changes

Hello @accelazh, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the project's Python version requirements, extending compatibility to include Python 3.13. The change reflects successful testing of the plugin with Python 3.13.8, ensuring that users running newer Python environments can continue to utilize the project without version conflicts.

Highlights

• Python Version Compatibility: The Python version constraint in pyproject.toml has been relaxed to allow compatibility with Python versions up to 3.13.x. Previously, the project was restricted to versions less than 3.13.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

• poetry.lock is excluded by !**/*.lock

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

Walkthrough

Raised the Python compatibility upper bound in pyproject.toml from <3.13 to <3.14. No other changes detected.

Changes

Cohort / File(s)	Summary of edits
Python compatibility bounds pyproject.toml	Updated [project] requires-python from >=3.11,<3.13 to >=3.11,<3.14.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I nibbled the bounds, a tiny hop higher,
From three-dot-thirteen to near-fourteen’s fire.
No deps disturbed, no gardens askew—
Just widening rows for versions anew.
Thump-thump! I sign this changelog trail,
A rabbit’s tweak with a whiskered tail. 🐇✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title clearly states the main change of the pull request by indicating the Python version constraint is being relaxed from <3.13 to <3.14. It concisely and accurately reflects the update made in pyproject.toml without extraneous details. The phrasing is specific enough for team members scanning the history to understand the PR’s intent.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

---

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.}

[gemini-code-assist]

Code Review

This pull request aims to relax the Python version constraint to include Python 3.13. While the change to pyproject.toml is a good first step, it is incomplete. The poetry.lock file has not been updated to reflect this change, which will cause inconsistencies and likely break builds for other contributors and in CI environments. It is critical to update the lock file before merging.