chore: release 0.9.0

[openfeaturebot]

🤖 I have created a release beep boop

0.9.0 (2026-04-16)

⚠ BREAKING CHANGES

• CLUSTER_DOMAIN env var is now FLAGD_CLUSTER_DOMAIN.

✨ New Features

• add flag metadata to FeatureFlag CRD (#808) (33168bb)
• add latest flagd config fields, bump deps (#818) (bf6c1ec)
• rename api module name (apis -> api) (#823) (70e9a3b)

🐛 Bug Fixes

• correct capabilities drop value to "ALL" for PodSecurity restricted compliance (#804) (0c87d05)
• envconfig: rename CLUSTER_DOMAIN env var to FLAGD_CLUSTER_DOMAIN (#792) (0668bd6)
• rename CLUSTER_DOMAIN env var to FLAGD_CLUSTER_DOMAIN (3cf6a6a)
• security: pin all GitHub Actions to SHA digests (#810) (9cd944a)
• Set appProtocol for service resources (#797) (fd99ee5)

🧹 Chore

• deps: pin dependencies (#812) (1047003)
• fix release-please config for apis module path (c25617e)
• latest flagd (#826) (c6a5601)
• release api 0.2.47 (#824) (3d77eda)
• release apis 0.2.46 (#816) (a9653a9)
• remove replace, use new module (#825) (38672cd)

---

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 automates the release of version 0.8.10 of the OpenFeature Operator. The primary change included in this release is a security enhancement that pins all GitHub Actions to their specific SHA digests, improving the integrity and security of the CI/CD pipeline. Additionally, this PR updates all relevant version references across the project's configuration and documentation to reflect the new release.

Highlights

• New Release: Version 0.8.10 of the OpenFeature Operator has been released.
• Security Fix: All GitHub Actions have been pinned to specific SHA digests to enhance security.

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.

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 appears to be an automated release for version 0.8.10. The version numbers have been updated correctly across all relevant files. However, there is an issue with the release date in the CHANGELOG.md file, which is set to a future date. This should be corrected before the release is finalized.

[gemini-code-assist]

The release date is set to a future date (2026-03-21). This is likely a typo and should be corrected to the current date. This seems to be a recurring issue, as the previous release also has a future date, which might indicate a misconfiguration in the release automation tool.

[openfeaturebot]

🤖 Release is at https://github.com/open-feature/open-feature-operator/releases/tag/v0.9.0 🌻