docs: move 1.6.3 related changelog

[aignas]

This fixes the changelog and manually changes the version updated tag.

The changes have been also cherry-picked to the release branch as I saw
release fail in the workflow. Hence this has become a 1.6.3 instead.

Fixes #3273

[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 focuses on refining the project's documentation by reorganizing the CHANGELOG.md file. It specifically relocates an important entry concerning the Minimal Version Selection (MVS) algorithm for PyPI wheels into a newly established section for the 1.6.2 release. This ensures that the release notes accurately reflect the changes included in that version, improving clarity and historical accuracy for users and contributors.

Highlights

• Changelog Reorganization: An entry detailing the Minimal Version Selection (MVS) algorithm for PyPI wheels has been moved within the CHANGELOG.md file.
• New Version 1.6.2 Section: A dedicated section for version 1.6.2 has been created in the CHANGELOG.md, dated 2025-09-21.
• Fix for Issue version 1.6.0+ with experimental_index_url are fetching incorrect wheels for glibc version #3250: The moved changelog entry specifically addresses and formalizes the fix for issue version 1.6.0+ with experimental_index_url are fetching incorrect wheels for glibc version #3250, related to PyPI wheel selection.

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

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 correctly moves a changelog entry for version 1.6.2 from the 'Unreleased' section to its own dedicated section. The change is straightforward and aligns with standard changelog maintenance. I've identified a minor typo in the moved text and suggested a correction for improved clarity.

[aignas]

I don't get how it happened but I was able to push to the main branch. I thought we had a setting that disallows that.

[rickeylev]

Oh weird, and alarming. Yeah, I thought so, too. I swear I've had it stop me before. Lets go check the settings.