chore(main): release 0.0.2

[openfeaturebot]

🤖 I have created a release beep boop

0.0.2 (2026-03-27)

Features

• add release-please configuration and manifest with initial version 0.0.1 (#85) (25425bf)

Bug Fixes

• remove $schema field from .release-please-manifest.json (#87) (28c283c)

---

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 represents the automated release of version 0.0.2 of the project. It updates the internal release manifest and generates a comprehensive changelog, documenting recent features and bug fixes, ensuring that the project's versioning and release notes are kept up-to-date automatically.

Highlights

• Automated Release: This pull request is an automated release generated by Release Please, bumping the project version to 0.0.2.
• Version Update: The internal release manifest has been updated to reflect the new version 0.0.2.
• Changelog Generation: A new CHANGELOG.md file has been created, detailing the features and bug fixes included in this release, specifically mentioning the addition of release-please configuration and a fix to the manifest schema.

Changelog

• .release-please-manifest.json
  • Updated the project version from 0.0.1 to 0.0.2.
• CHANGELOG.md
  • Added the changelog for version 0.0.2, including details on the release-please configuration feature and a bug fix for the manifest schema.

Activity

• This pull request was automatically generated by the Release Please bot to create a new 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 is an automated release for version 0.0.2. The changes include updating the version manifest and adding a new changelog. I've noticed a minor formatting issue in the CHANGELOG.md file with extra newlines and have provided a suggestion to improve its readability.

[gemini-code-assist]

There are some extra blank lines in the generated changelog. For better readability and consistent formatting, it's best to use only a single blank line to separate blocks. I've provided a suggestion to clean this up.

Suggested change

	## [0.0.2](https://github.com/open-feature/cpp-sdk/compare/v0.0.1...v0.0.2) (2026-03-12)
	### Features
	* add release-please configuration and manifest with initial version 0.0.1 ([#85](https://github.com/open-feature/cpp-sdk/issues/85)) ([25425bf](https://github.com/open-feature/cpp-sdk/commit/25425bf2100476123c3df2cb3e8caf55bfb7d575))
	### Bug Fixes
	* remove $schema field from .release-please-manifest.json ([#87](https://github.com/open-feature/cpp-sdk/issues/87)) ([28c283c](https://github.com/open-feature/cpp-sdk/commit/28c283c428993ec46775aa8d275765a24f340ee0))
	## [0.0.2](https://github.com/open-feature/cpp-sdk/compare/v0.0.1...v0.0.2) (2026-03-12)
	### Features
	* add release-please configuration and manifest with initial version 0.0.1 ([#85](https://github.com/open-feature/cpp-sdk/issues/85)) ([25425bf](https://github.com/open-feature/cpp-sdk/commit/25425bf2100476123c3df2cb3e8caf55bfb7d575))
	### Bug Fixes
	* remove $schema field from .release-please-manifest.json ([#87](https://github.com/open-feature/cpp-sdk/issues/87)) ([28c283c](https://github.com/open-feature/cpp-sdk/commit/28c283c428993ec46775aa8d275765a24f340ee0))