chore(main): release 4.0.0

[openfeaturebot]

🤖 I have created a release beep boop

4.0.0 (2026-03-04)

⚠ BREAKING CHANGES

• make default variant optional (#333)

🐛 Bug Fixes

• Add @sync-port tag to in-process scenarios (#314) (3af557a)
• Add fatalStatusCodes tags in config gherkin (#316) (49764f6)
• correct default retryBackoffMaxMs value (7408867)
• deadlock if /change is called during /restart (#321) (4583da2)
• make file update atomic, wait for /start (#329) (64011fa)
• more possible change deadlocks (#324) (e103d93)
• race condition in /stop (#327) (8bafdaf)
• Refactor in-process sync port scenarios (#318) (1f6845c)
• release please (#298) (074fe66)
• release please (#299) (3962ad3)
• remove file mode from forbidden flagd connection test (#312) (1759a94)
• replace githubaction with newer version (#290) (95d0fa1)
• revert ends_with non-string change (14eb032)
• update base, fix permissions issue (#335) (fc91669)

✨ New Features

• add envoy via docker compose (#283) (27b764b)
• 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)
• Envoy connection lost test added (needs working targetURI) (#300) (7565c27)
• improve forbidden with options (#304) (00b7cfb)
• make default variant optional (#333) (f0a1dde)
• Support multi-platform build (#313) (e1ff79c)

🧹 Chore

• add CODEOWNERS (89c9af6)
• add docker compose to release please config (#284) (8580989)
• add test to ensure fatal state on forbidden error (#756) (#302) (446a9f5)
• deps: update google-github-actions/release-please-action action to v4 (#86) (690a2b4)
• fix version in docker compose for update (#285) (de20bec)
• fix version in docker compose for update (#286) (34bfe79)
• fix version in docker compose for update (#287) (4233c92)
• main: release 2.12.0 (#282) (fdce987)
• main: release 2.13.0 (#301) (b62f5db)
• main: release 2.13.1 (#303) (c7620ba)
• main: release 2.14.0 (#305) (bde8977)
• main: release 2.15.0 (#309) (6948dcb)
• main: release 2.15.1 (#315) (4f3f555)
• main: release 2.15.2 (#317) (7d7d518)
• main: release 2.15.3 (#319) (9b73b3a)
• main: release 2.15.4 (#322) (95963d7)
• main: release 2.15.5 (#323) (2b67574)
• main: release 2.15.6 (#325) (b0057ab)
• main: release 2.15.7 (#326) (6515f91)
• main: release 2.15.8 (#328) (e1bfc39)
• main: release 2.15.9 (#330) (ecb3d09)
• main: release 3.0.0 (#334) (9799fcc)
• main: release 3.0.1 (#336) (ca08485)

---

This PR was generated with Release Please. See documentation.

[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 marks the release of version 4.0.0, incorporating a significant breaking change related to variant handling. It also delivers a comprehensive set of bug fixes to enhance stability and reliability, alongside several new features that expand functionality and improve build processes. The changes aim to refine the overall experience and capabilities of the system.

Highlights

• Breaking Change: The default variant has been made optional, which is a breaking change.
• Bug Fixes: Addressed several issues including deadlocks during /change and /restart operations, a race condition in /stop, and ensured atomic file updates. Also corrected the default retryBackoffMaxMs value and refined in-process sync port scenarios.
• New Features: Introduced Envoy integration via Docker Compose, added support for FLAGD_BASE_IMAGE build argument and FLAGD_SYNC_PORT for in-process providers, and enabled multi-platform builds. New tests for Envoy connection loss and improved forbidden options were also added.
• Chores and Maintenance: Updated the google-github-actions/release-please-action to v4, added CODEOWNERS, and included docker compose in the release please configuration. Multiple minor releases (2.12.0 through 3.0.1) were also performed as part of the release process.

Changelog

• BREAKING CHANGES
  • make default variant optional (#333)
• Bug Fixes
  • Add @sync-port tag to in-process scenarios (#314)
  • Add fatalStatusCodes tags in config gherkin (#316)
  • correct default retryBackoffMaxMs value
  • deadlock if /change is called during /restart (#321)
  • make file update atomic, wait for /start (#329)
  • more possible change deadlocks (#324)
  • race condition in /stop (#327)
  • Refactor in-process sync port scenarios (#318)
  • release please (#298)
  • release please (#299)
  • remove file mode from forbidden flagd connection test (#312)
  • replace githubaction with newer version (#290)
  • revert ends_with non-string change
  • update base, fix permissions issue (#335)
• Chore
  • add CODEOWNERS
  • add docker compose to release please config (#284)
  • add test to ensure fatal state on forbidden error (#756) (#302)
  • update google-github-actions/release-please-action action to v4 (#86)
  • fix version in docker compose for update (#285)
  • fix version in docker compose for update (#286)
  • fix version in docker compose for update (#287)
  • release 2.12.0 (#282)
  • release 2.13.0 (#301)
  • release 2.13.1 (#303)
  • release 2.14.0 (#305)
  • release 2.15.0 (#309)
  • release 2.15.1 (#315)
  • release 2.15.2 (#317)
  • release 2.15.3 (#319)
  • release 2.15.4 (#322)
  • release 2.15.5 (#323)
  • release 2.15.6 (#325)
  • release 2.15.7 (#326)
  • release 2.15.8 (#328)
  • release 2.15.9 (#330)
  • release 3.0.0 (#334)
  • release 3.0.1 (#336)
• New Features
  • add envoy via docker compose (#283)
  • Add FLAGD_BASE_IMAGE build argument to Dockerfile (#308)
  • Add FLAGD_SYNC_PORT support for in-process providers with backwards compatibility (#310)
  • add missing steps for config and improve wording (#311)
  • Envoy connection lost test added (needs working targetURI) (#300)
  • improve forbidden with options (#304)
  • make default variant optional (#333)
  • Support multi-platform build (#313)

Activity

• This pull request was automatically generated by Release Please, indicating a new version release.

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 updates the project version to 4.0.0 across the .release-please-manifest.json, CHANGELOG.md, docker-compose.yaml, and version.txt files. These changes are consistent with a new release and appear to be purely administrative version bumps.