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

[openfeaturebot]

🤖 I have created a release beep boop

0.0.2 (2026-02-19)

🐛 Bug Fixes

• security: update dependency org.assertj:assertj-core to v3.27.7 [security] (#1700) (57e6287)

✨ 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 performs an automated release of the dev.openfeature.contrib.tools.flagdcore package, incrementing its version to 0.0.2. This update primarily incorporates a new feature that extracts core flagd evaluation and API modules, improving the structure and capabilities of the flagd-core component.

Highlights

• New Feature: The flagd-core module now includes extracted core flagd evaluation and API modules, enhancing modularity and functionality (issue feat: extract core flagd evaluation and API modules #1696).
• Version Update: The dev.openfeature.contrib.tools.flagdcore package has been released as version 0.0.2.

Changelog

• tools/flagd-core/CHANGELOG.md
  • ✨ New Features
  • extract core flagd evaluation and API modules (#1696) (fe98d88)

Activity

• Automated release initiated by openfeaturebot using Release Please.

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, generated by Release Please, updates the version of dev.openfeature.contrib.tools.flagdcore to 0.0.2. The changes are mostly version bumps in configuration and documentation files. I've found a couple of issues in the CHANGELOG.md file: the release date is set in the future, and a redundant heading has been added. These should be corrected to ensure the changelog is accurate and clean.

[gemini-code-assist]

The release date is set to 2026-02-18, which is in the future. This should be corrected to the actual release date.

[gemini-code-assist]

This ## Changelog heading is redundant as the file already begins with # Changelog on line 1. It should be removed to improve clarity.