chore: release 1.7 prep

[rickeylev]

• Update changelog
• Update version markers

Work towards #3338

[gemini-code-assist]

Summary of Changes

Hello @rickeylev, 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 is a preparatory step for the 1.7.0 release. It focuses on updating all relevant version markers and the changelog to align with the new release number. This ensures that all new features, changes, and fixes are correctly attributed to the 1.7.0 release in the documentation and internal configuration.

Highlights

• Changelog Update: The CHANGELOG.md file has been updated to reflect the upcoming 1.7.0 release, moving previously unreleased changes under the new version heading and setting the release date to 2025-10-11.
• Version Marker Standardization: Various documentation and configuration files have had their VERSION_NEXT_FEATURE placeholders replaced with the explicit 1.7.0 version number, ensuring consistency across the project for the new release.

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

[gemini-code-assist]

Code Review

This pull request prepares for the 1.7 release by updating the changelog and version markers across the codebase. The changes are mostly mechanical and look correct. I've suggested one improvement to the changelog to add a new 'Unreleased' section, which will make it easier for future contributions.

[gemini-code-assist]

To prepare for the next release, it's good practice to add a new 'Unreleased' section at the top of the changelog. This makes it easy for contributors to add their changes for the next version.

{#v0-0-0} ## Unreleased [0.0.0]: https://github.com/bazel-contrib/rules_python/releases/tag/0.0.0 {#v0-0-0-removed} ### Removed * Nothing removed. {#v0-0-0-changed} ### Changed * Nothing changed. {#v0-0-0-fixed} ### Fixed * Nothing fixed. {#v0-0-0-added} ### Added * Nothing added. {#v1-7-0}