Skip to content

chore(main): release 2.14.0#305

Merged
toddbaert merged 1 commit intomainfrom
release-please--branches--main
Oct 30, 2025
Merged

chore(main): release 2.14.0#305
toddbaert merged 1 commit intomainfrom
release-please--branches--main

Conversation

@openfeaturebot
Copy link
Contributor

🤖 I have created a release beep boop

2.14.0 (2025-10-30)

✨ New Features


This PR was generated with Release Please. See documentation.

Signed-off-by: OpenFeature Bot <109696520+openfeaturebot@users.noreply.github.com>
@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.14.0 of the project. It primarily updates version numbers in various project files and integrates a new feature that enhances handling of 'forbidden with options'. The changes ensure that the project's manifest, changelog, Docker image reference, and version tracking are all aligned with the new release.

Highlights

  • Version Bump: The project version has been updated from 2.13.1 to 2.14.0 across relevant configuration files and the changelog.
  • New Feature Inclusion: This release incorporates a new feature described as 'improve forbidden with options', which was tracked under issue feat: improve forbidden with options #304.
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.

@toddbaert toddbaert merged commit bde8977 into main Oct 30, 2025
3 checks passed
@openfeaturebot
Copy link
Contributor Author

🤖 Created releases:

🌻

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 updates the version of the flagd-testbed to 2.14.0. The changes include updating the version in .release-please-manifest.json, CHANGELOG.md, docker-compose.yaml, and version.txt. I have added comments regarding the version updates in docker-compose.yaml.

services:
flagd:
image: ${IMAGE:-ghcr.io/open-feature/flagd-testbed}:${VERSION:-v2.13.1} # x-release-please-version
image: ${IMAGE:-ghcr.io/open-feature/flagd-testbed}:${VERSION:-v2.14.0} # x-release-please-version

Choose a reason for hiding this comment

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

high

high: Consider using a consistent approach for versioning. While the # x-release-please-version comment is helpful, it might be better to rely solely on the ${VERSION} environment variable for specifying the image version. This would ensure that the version used in the docker-compose file is always in sync with the environment.

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.

2 participants