Skip to content

chore(main): release open-feature-flipt 0.2.0#79

Closed
openfeaturebot wants to merge 1 commit into
mainfrom
release-please--branches--main--components--open-feature-flipt
Closed

chore(main): release open-feature-flipt 0.2.0#79
openfeaturebot wants to merge 1 commit into
mainfrom
release-please--branches--main--components--open-feature-flipt

Conversation

@openfeaturebot

@openfeaturebot openfeaturebot commented Nov 1, 2025

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.2.0 (2026-06-23)

⚠ BREAKING CHANGES

  • Update dependencies and fix flaky retry mechanism tests (#74)

✨ New Features

  • flagd: Cargo features for evaluation modes (#88) (6ba9d48)

🧹 Chore

  • Update dependencies and fix flaky retry mechanism tests (#74) (9b78024)

This PR was generated with Release Please. See documentation.

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @openfeaturebot, I'm Gemini Code Assist1! 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.2.0 for the open-feature-flipt crate. The update incorporates significant dependency upgrades and addresses a previously flaky retry mechanism, which together constitute a breaking change. This ensures the project's dependencies are current and improves the reliability of the retry logic.

Highlights

  • New Release: The open-feature-flipt crate has been released as version 0.2.0.
  • Breaking Changes: This release includes breaking changes related to updated dependencies and a fix for a flaky retry mechanism, as detailed in issue chore!: Update dependencies and fix flaky retry mechanism tests #74.
  • Version Updates: The version has been updated in .release-please-manifest.json and crates/flipt/Cargo.toml to reflect the new 0.2.0 release.
  • Changelog Addition: A new CHANGELOG.md file has been added for the crates/flipt package, documenting the 0.2.0 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 gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request is an automated release for open-feature-flipt version 0.2.0. The changes correctly update the version in Cargo.toml and .release-please-manifest.json, and add a corresponding CHANGELOG.md. The changes appear correct for a release. I have one minor suggestion to improve the formatting of the changelog.

Comment thread crates/flipt/CHANGELOG.md

## [0.2.0](https://github.com/open-feature/rust-sdk-contrib/compare/open-feature-flipt-v0.1.0...open-feature-flipt-v0.2.0) (2025-11-01)


Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This extra blank line can be removed to improve the compactness of the changelog.

@openfeaturebot openfeaturebot force-pushed the release-please--branches--main--components--open-feature-flipt branch 2 times, most recently from 69186e0 to 31af79f Compare November 12, 2025 17:09
@openfeaturebot openfeaturebot force-pushed the release-please--branches--main--components--open-feature-flipt branch 2 times, most recently from c46b2cb to 21472e4 Compare November 18, 2025 14:34
@openfeaturebot openfeaturebot force-pushed the release-please--branches--main--components--open-feature-flipt branch 2 times, most recently from 432cf7f to 5d6e5c0 Compare December 1, 2025 08:42
@openfeaturebot openfeaturebot force-pushed the release-please--branches--main--components--open-feature-flipt branch 2 times, most recently from d781970 to a627680 Compare December 12, 2025 21:36
@openfeaturebot openfeaturebot force-pushed the release-please--branches--main--components--open-feature-flipt branch 2 times, most recently from d22b60d to 660df86 Compare December 29, 2025 12:24
@openfeaturebot openfeaturebot force-pushed the release-please--branches--main--components--open-feature-flipt branch from 660df86 to d7a79b2 Compare January 7, 2026 08:31
@openfeaturebot openfeaturebot force-pushed the release-please--branches--main--components--open-feature-flipt branch from d7a79b2 to 4cebd8e Compare March 1, 2026 10:25
@openfeaturebot openfeaturebot force-pushed the release-please--branches--main--components--open-feature-flipt branch 3 times, most recently from c7298ec to b782c66 Compare March 16, 2026 12:18
@openfeaturebot openfeaturebot force-pushed the release-please--branches--main--components--open-feature-flipt branch from b782c66 to 92bc27c Compare April 9, 2026 06:36
Signed-off-by: OpenFeature Bot <109696520+openfeaturebot@users.noreply.github.com>
@openfeaturebot openfeaturebot force-pushed the release-please--branches--main--components--open-feature-flipt branch from 92bc27c to 6952183 Compare June 23, 2026 19:07
@coderabbitai

coderabbitai Bot commented Jun 23, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

Bumps the open-feature-flipt crate version from 0.1.0 to 0.2.0 in Cargo.toml and .release-please-manifest.json, and adds a 0.2.0 changelog entry dated 2026-06-23 covering breaking dependency changes, new flagd Cargo features, and a flaky retry test fix.

Changes

open-feature-flipt 0.2.0 Release

Layer / File(s) Summary
Version and changelog update
crates/flipt/Cargo.toml, .release-please-manifest.json, crates/flipt/CHANGELOG.md
Package version incremented to 0.2.0 in both the crate manifest and the release-please manifest; CHANGELOG.md populated with the 0.2.0 release entry including breaking changes, new flagd evaluation mode Cargo features, and chore items.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main change: an automated release bump of the open-feature-flipt package from 0.1.0 to 0.2.0, which is directly reflected in the version updates across all changed files.
Description check ✅ Passed The description is directly related to the changeset, detailing the 0.2.0 release with breaking changes, new features, and chore updates that correspond to the file modifications shown in the PR.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@crates/flipt/Cargo.toml`:
- Line 3: The crate version has been bumped to 0.2.0 in the Cargo.toml file, but
the installation documentation in crates/flipt/README.md still references the
old version 0.1.0. Update the dependency version in the README.md installation
example from open-feature-flipt="0.1.0" to open-feature-flipt="0.2.0" to ensure
users download the correct version when following the installation instructions.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: b5fb011c-5e86-4328-ac1b-cc220de8eb1c

📥 Commits

Reviewing files that changed from the base of the PR and between 867b37b and 6952183.

📒 Files selected for processing (3)
  • .release-please-manifest.json
  • crates/flipt/CHANGELOG.md
  • crates/flipt/Cargo.toml

Comment thread crates/flipt/Cargo.toml
[package]
name = "open-feature-flipt"
version = "0.1.0"
version = "0.2.0"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Update installation docs to match the new crate version.

Line 3 bumps to 0.2.0, but crates/flipt/README.md still shows open-feature-flipt="0.1.0" in installation guidance, which can send users to the previous release.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@crates/flipt/Cargo.toml` at line 3, The crate version has been bumped to
0.2.0 in the Cargo.toml file, but the installation documentation in
crates/flipt/README.md still references the old version 0.1.0. Update the
dependency version in the README.md installation example from
open-feature-flipt="0.1.0" to open-feature-flipt="0.2.0" to ensure users
download the correct version when following the installation instructions.

@erenatas erenatas closed this Jun 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants