bazelbuild
feat(toolchains): Add 3.13.10, 3.13.11, 3.14.1, 3.15.0a2
Summary of Changes
Hello @pjjw, I'm Gemini Code Assist[^1]! 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 expands the available Python toolchains by integrating version 3.13.11. This update ensures that developers have access to the latest stable Python release, providing updated runtime options and maintaining compatibility across diverse operating systems and architectures for building and testing applications.
Highlights
- New Python Version Support: Added support for Python version 3.13.11 to the project's toolchain definitions.
- Comprehensive Platform Coverage: Included URL, SHA256 checksums, and strip_prefix configurations for Python 3.13.11 across a wide range of platforms and build types, including various Linux distributions (GNU, Musl), macOS, and Windows, with both standard and freethreaded variants.
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 :thumbsup: and :thumbsdown: 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.
[^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[bot] avatar](https://avatars.githubusercontent.com/in/956858?v=4 "Published by a pub.dev verified publisher"){kind=small}
CI is failing on tests/python/python_tests.bzl -- I think MINOR_MAPPING needs to be updated to point to the latest versions. By default, the bzlmod selection logic takes the highest version listed in TOOL_VERSIONS.
CI is failing on tests/python/python_tests.bzl -- I think MINOR_MAPPING needs to be updated to point to the latest versions. By default, the bzlmod selection logic takes the highest version listed in TOOL_VERSIONS.
done, still seems like some trouble with the 3.14 toolchains, though, and haven't had a ton of time to debug (just carrying a local patch in our repo for the moment)
oops. very silly problem. blank checksums in the 3.14.1 release b/c i was going off the release notes for when the version was added, not the actual released files.. https://github.com/astral-sh/python-build-standalone/releases/tag/20251205