Skip to content

chore(main): release 3.0.0#334

Merged
toddbaert merged 1 commit intomainfrom
release-please--branches--main
Mar 4, 2026
Merged

chore(main): release 3.0.0#334
toddbaert merged 1 commit intomainfrom
release-please--branches--main

Conversation

@openfeaturebot
Copy link
Contributor

🤖 I have created a release beep boop

3.0.0 (2026-03-04)

⚠ BREAKING CHANGES

  • make default variant optional (#333)

✨ 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, 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 automates the release of version 3.0.0 for the flagd-testbed, incorporating a significant breaking change and a new feature related to making the default variant optional. It updates various configuration and documentation files to reflect this new major version, ensuring consistency across the project.

Highlights

  • Breaking Change: The default variant has been made optional, which may require adjustments in existing configurations.
  • New Feature: Introduced the capability to make the default variant optional, enhancing configuration flexibility.
Changelog
  • .release-please-manifest.json
    • Updated the tracked version to 3.0.0.
  • CHANGELOG.md
    • Added a new entry for version 3.0.0, detailing a breaking change and a new feature regarding optional default variants.
  • docker-compose.yaml
    • Updated the flagd image version to 3.0.0.
  • version.txt
    • Updated the project version to 3.0.0.
Activity
  • This pull request was automatically generated by Release Please to create version 3.0.0.
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 9799fcc into main Mar 4, 2026
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 automates the release of version 3.0.0. The changes correctly update the version number in .release-please-manifest.json, docker-compose.yaml, and version.txt. The CHANGELOG.md is also updated with the new release information. My review includes one suggestion regarding the release date in the changelog, which appears to be set in the future.

@@ -1,5 +1,16 @@
# Changelog

## [3.0.0](https://github.com/open-feature/flagd-testbed/compare/v2.15.9...v3.0.0) (2026-03-04)

Choose a reason for hiding this comment

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

medium

The release date is set to a future date (2026-03-04). This appears to be a recurring issue in the changelog, likely due to a misconfiguration in the release automation. To avoid confusing users, release dates should reflect the actual date of the release.

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