chore(main): release 2.15.6

[openfeaturebot]

🤖 I have created a release beep boop

2.15.6 (2026-01-06)

🐛 Bug Fixes

• more possible change deadlocks (#324) (e103d93)

---

This PR was generated with Release Please. See documentation.

[gemini-code-assist]

Summary of Changes

Hello @openfeaturebot, 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 is an automated release for version 2.15.6 of the project. Its main purpose is to publish the latest stable version, which includes a critical bug fix related to potential change deadlocks. The changes ensure that all relevant project metadata and configuration files are aligned with the new version number, facilitating a smooth update process for users.

Highlights

• Version Release: This pull request automates the release of version 2.15.6 for the project.
• Bug Fix Inclusion: The new release incorporates a bug fix addressing 'more possible change deadlocks', as detailed in issue fix: more possible change deadlocks #324.
• Version Updates: Key project files, including the release manifest, changelog, Docker Compose configuration, and version tracking file, have been updated to reflect the new 2.15.6 version.

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

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 is an automated release for version 2.15.6. The changes correctly update the version number in .release-please-manifest.json, docker-compose.yaml, and version.txt. I've noted a potential issue in the CHANGELOG.md where the release date seems to be static across the last few releases, which may indicate a misconfiguration in the release automation. Otherwise, the changes are consistent and look correct for a patch release.

[gemini-code-assist]

The release date (2026-01-06) appears to be incorrect as it is identical to the dates for the previous versions 2.15.5 and 2.15.4. This suggests a possible misconfiguration in the release automation process which is causing the date not to be updated for new releases. It would be good to investigate the release-please configuration to ensure release dates are generated correctly.

[openfeaturebot]

🤖 Created releases:

• v2.15.6

🌻