docs: Potential fixes for 2 code quality findings in CHANGELOG.md

[Pr0methean]

This PR applies 2/2 suggestions from code quality AI findings.

[gemini-code-assist]

Summary of Changes

Hello @Pr0methean, 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, according to its description, aims to address two code quality findings identified by AI. However, the provided patch exclusively focuses on updates to the CHANGELOG.md file. These updates include the addition of a new version header for 2.6.0 and a minor correction to a pull request link within an existing 2.5.0 entry.

Highlights

• Changelog Update for Version 2.6.0: A new version entry for 2.6.0 has been added to the CHANGELOG.md file, dated 2025-03-30, initially marked with "No documented changes."
• Changelog Link Correction: An existing entry in the CHANGELOG.md for version 2.5.0 has been updated to correctly link to pull request #267 for the DateTime refactor.

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

[amazon-q-developer]

This PR correctly addresses two documentation issues in the CHANGELOG.md:

1. Missing version entry: Adds the missing 2.6.0 changelog entry that was released but not documented
2. Link formatting: Fixes the missing link reference for PR #267

The changes are properly formatted and maintain consistency with the existing changelog structure. Both fixes improve the documentation quality without affecting functionality.

Note: The PR title should follow Conventional Commits format with a docs: prefix for documentation changes, as specified in the project guidelines.

---

You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.

[gemini-code-assist]

Code Review

This pull request addresses two documentation issues in CHANGELOG.md by adding a missing version entry and making a link consistent with others. The changes are beneficial. I have one minor suggestion to improve the formatting of the new version entry for better consistency with the rest of the file.