Skip to content

Conversation

@openfeaturebot
Copy link
Contributor

@openfeaturebot openfeaturebot commented Nov 3, 2025

πŸ€– I have created a release beep boop

2.15.0 (2025-11-21)

πŸ› Bug Fixes

  • remove file mode from forbidden flagd connection test (#312) (1759a94)

✨ New Features

  • Add FLAGD_BASE_IMAGE build argument to Dockerfile (#308) (779adad)
  • Add FLAGD_SYNC_PORT support for in-process providers with backwards compatibility (#310) (513f2a9)
  • add missing steps for config and improve wording (#311) (c1f632b)
  • Support multi-platform build (#313) (e1ff79c)

This PR was generated with Release Please. See documentation.

@openfeaturebot openfeaturebot force-pushed the release-please--branches--main branch from 0598e06 to a911fda Compare November 3, 2025 05:38
@openfeaturebot openfeaturebot requested a review from a team as a code owner November 3, 2025 05:38
@gemini-code-assist
Copy link

Summary of Changes

Hello @openfeaturebot, I'm Gemini Code Assist1! 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 represents an automated release for version 2.15.0 of the project. It primarily involves updating version numbers across various configuration files and the changelog to reflect a new feature: the ability to specify a base image for the Dockerfile. This ensures that all project components are aligned with the latest release.

Highlights

  • Version Update: The project version has been updated from 2.14.0 to 2.15.0 across all relevant configuration files, including .release-please-manifest.json and version.txt.
  • Changelog Entry: The CHANGELOG.md has been updated to include the new 2.15.0 release, highlighting the addition of the FLAGD_BASE_IMAGE build argument to the Dockerfile.
  • Docker Compose Image Reference: The docker-compose.yaml file now references the newly released v2.15.0 image for the flagd service.
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. ↩

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request contains automated version bumps for the 2.15.0 release. The changes correctly update the version in the project's manifest, Docker Compose file, version file, and changelog. I have one minor suggestion for the CHANGELOG.md file to improve its formatting and align it with common Markdown standards.


## [2.15.0](https://github.com/open-feature/flagd-testbed/compare/v2.14.0...v2.15.0) (2025-11-03)


Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

To align with common Markdown styling conventions, such as the 'Keep a Changelog' standard, it's recommended to use a single blank line between headings. This improves the readability of the changelog.

@openfeaturebot openfeaturebot force-pushed the release-please--branches--main branch from a911fda to c622bb9 Compare November 12, 2025 14:10
@openfeaturebot openfeaturebot force-pushed the release-please--branches--main branch 2 times, most recently from 54fcb90 to a66d5c4 Compare November 21, 2025 10:11
Signed-off-by: OpenFeature Bot <[email protected]>
@openfeaturebot openfeaturebot force-pushed the release-please--branches--main branch from a66d5c4 to 2d43e11 Compare November 21, 2025 12:23
@aepfli aepfli merged commit 6948dcb into main Nov 21, 2025
4 checks passed
@openfeaturebot
Copy link
Contributor Author

πŸ€– Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants