Create 2026_03_18.md

[clairerye]

release notes

[gemini-code-assist]

Summary of Changes

Hello, 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 release notes for the AGDR platform's March 18, 2026 update. It primarily documents the integration of the REMS system for managing data access and submission applications, alongside a comprehensive list of updated versions for various core components and internal microservices, ensuring transparency and clarity regarding the current state of the platform.

Highlights

• New Release Notes Document: A new Markdown file, 2026_03_18.md, has been added to the docs/release_notes directory, documenting the AGDR release for March 18, 2026.
• REMS Integration: The release notes highlight the integration of REMS (Research Electronic Management System) to manage applications for data access and submission.
• Version Updates: Various system components, including Dictionary, Submission (sheepdog), Portal, AGDR Internal helm chart, REMS, and several internal microservices like indexd, fence, arborist, peregrine, sheepdog, guppy, nginx, tube, spark, manifestservice, metadata, and postgres, have had their versions updated and documented.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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.

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 introduces the release notes for March 18, 2026. The content appears correct for a release note. I've added a few suggestions to improve the markdown formatting for consistency and readability by removing superfluous blank lines and whitespace.

[gemini-code-assist]

There is an extra blank line here between the main versions list and the micro-services list. Using a single blank line for separation is more conventional and improves source readability. Please consider removing this superfluous line.

[gemini-code-assist]

Similar to a previous comment, there is an extra blank line here. For consistency and cleaner source code, it's recommended to use only a single blank line to separate sections.

[gemini-code-assist]

This line consists only of whitespace characters. While many Markdown parsers treat this as a blank line, it's best practice to use a truly empty line for this purpose. This avoids ambiguity and potential issues with tools that trim trailing whitespace.