fix(doc): fix the release notes for the starlarkification of the flags

[aignas]

It seems that the changelog got merged for 1.7.0, but the
VERSION_NEXT_FEATURE got added to the docs instead of 1.7.0. This is fixing
that so that we can merge/cherry-pick again to the release branch.

[gemini-code-assist]

Summary of Changes

Hello @aignas, 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 addresses a documentation oversight where a generic version placeholder was used instead of the specific 1.7.0 release number within the rules_python API documentation. The change updates all instances of VERSION_NEXT_FEATURE to 1.7.0 for versionadded and deprecated tags, ensuring that the documentation accurately reflects the correct release information and facilitates smooth release management.

Highlights

• Documentation Correction: The pull request corrects an error in the documentation where the placeholder VERSION_NEXT_FEATURE was mistakenly used instead of the actual version number 1.7.0 for several flag-related entries.
• Release Notes Accuracy: This fix ensures the accuracy of release notes for version 1.7.0, which is critical for proper merging and cherry-picking to the release branch.

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 provides a documentation fix, updating several versionadded and deprecated directives in docs/api/rules_python/python/config_settings/index.md. The placeholder VERSION_NEXT_FEATURE is correctly replaced with the specific version 1.7.0. These changes accurately reflect the version in which the starlarkified flags were introduced, as described in the pull request. The changes are correct and I have no suggestions for improvement.