chore(ci): matrix test on py 3.13 and 3.14

[Kevin James (TheKevJames)]

Summary

Add 3.13 and 3.14 to our matrix targets.

[gemini-code-assist]

Summary of Changes

Hello, 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 enhances the continuous integration pipeline by integrating support for newer Python versions, specifically 3.13 and 3.14. This update ensures that the project's builds and tests are run against the latest stable Python releases, improving compatibility and future-proofing the CI environment.

Highlights

• New Python Version Support: Added dedicated executors for Python 3.13.12 and Python 3.14.3 within the CircleCI configuration.
• CI Job Executor Updates: Updated the python-integration, build-rest, poetry-publish-workspace, and docs jobs to utilize the newly defined python314 executor, standardizing on a newer Python version for these tasks.
• Expanded Test Matrix: Extended the test-unit-aio and test-unit-rest workflow matrices to include Python 3.13 and 3.14, ensuring broader compatibility testing for unit tests.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• .circleci/config.yml
  • Added new python313 and python314 executors.
  • Updated the python-integration executor to use python:3.14.3.
  • Changed build-rest, poetry-publish-workspace, and docs jobs to use the python314 executor.
  • Expanded the test-unit-aio and test-unit-rest workflow matrices to include python313 and python314.

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 (@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 (@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. ↩

[gemini-code-assist]

Code Review

This pull request adds Python 3.13 and 3.14 to the CI test matrix. While testing against upcoming Python versions is a good practice, the specified Docker image tags (python:3.13.12 and python:3.14.3) are invalid because these specific versions have not been released and the tags do not exist on Docker Hub. This will cause the CI pipeline to fail. My review includes suggestions to use a valid pre-release tag for Python 3.13 and to remove the changes related to Python 3.14 for now, as no official images are available for it yet. These changes affect not only the executor definitions but also several jobs that have been updated to use the new python314 executor.