chore(main): release dev.openfeature.contrib.tools.flagdapi 0.0.2

[openfeaturebot]

🤖 I have created a release beep boop

0.0.2 (2026-02-19)

✨ New Features

• extract core flagd evaluation and API modules (#1696) (fe98d88)

---

This PR was generated with Release Please. See documentation.

[gemini-code-assist]

Summary of Changes

Hello @openfeaturebot, 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 the dev.openfeature.contrib.tools.flagdapi module to version 0.0.2. This release incorporates a significant new feature that involves the extraction of core flagd evaluation and API modules, improving the structure and capabilities of the component. The changes primarily involve updating version numbers across various configuration and documentation files to reflect this new release.

Highlights

• New Release: The dev.openfeature.contrib.tools.flagdapi module has been released as version 0.0.2.
• New Feature: Core flagd evaluation and API modules have been extracted, enhancing modularity and functionality.

Changelog

• .release-please-manifest.json
  • Updated the version of tools/flagd-api to 0.0.2.
• tools/flagd-api/CHANGELOG.md
  • Added a new changelog entry for version 0.0.2.
  • Documented the new feature: extraction of core flagd evaluation and API modules.
• tools/flagd-api/README.md
  • Updated the dependency version in the usage example to 0.0.2.
• tools/flagd-api/pom.xml
  • Updated the project version to 0.0.2.
• tools/flagd-api/version.txt
  • Updated the version string to 0.0.2.

Activity

• This pull request was automatically generated by Release Please to create a new release for dev.openfeature.contrib.tools.flagdapi.

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

The pull request correctly updates the version of the flagd-api module to 0.0.2 across all relevant files, including the manifest, POM, README, and version file. The changes are consistent with the release of the new feature described. I have identified a redundant header in the CHANGELOG.md file that should be removed to maintain documentation clarity.

[gemini-code-assist]

The ## Changelog header at the end of the file is redundant as the file already starts with a # Changelog header. This appears to be a formatting artifact from the automated changelog generation.