Create 2025_10_29.md

[clairerye]

release notes

[gemini-code-assist]

Summary of Changes

Hello @clairerye, 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 introduces the official release notes for October 29, 2025, by adding a new Markdown document. The notes provide a detailed overview of updated component versions across the system, from core services to internal micro-services and databases, alongside highlighting new user-facing features such as an enhanced footer and new geographic data visualization capabilities.

Highlights

• New Release Notes Document: A new Markdown file, "2025_10_29.md", has been added to the "docs/release_notes" directory, serving as the official release notes for October 29, 2025.
• Version Updates: The release notes document comprehensive version updates for various components, including the Dictionary, Submission (sheepdog), Portal, and numerous internal micro-services like indexd, fence, arborist, peregrine, guppy, and more, along with database versions.
• New Features and Improvements: Two key improvements are highlighted: an updated footer with new logos and text, and the introduction of geographic location sliders at the sample level.

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 adds a new release notes file. The content is clear, but I've identified a few minor formatting and consistency issues. My feedback includes suggestions to remove unnecessary whitespace and correct the naming and formatting of a service to improve the overall readability and consistency of the document.

[gemini-code-assist]

This extra blank line is unnecessary and can be removed to make the document more compact and improve the source readability.

[gemini-code-assist]

For consistency and correctness, 'elastic search' should be written as 'Elasticsearch'. Additionally, the space before the colon is inconsistent with other items in this list.

Suggested change

	- elastic search : elasticsearch-oss:7.10.2
	- Elasticsearch: elasticsearch-oss:7.10.2

[gemini-code-assist]

This line contains unnecessary leading whitespace. To ensure consistent rendering across different markdown parsers, this indented blank line should be removed or replaced with a simple blank line.