Skip to content

chore(main): release 0.6.0#218

Merged
josecolella merged 1 commit intomainfrom
release-please--branches--main--components--openfeature-sdk
Mar 5, 2026
Merged

chore(main): release 0.6.0#218
josecolella merged 1 commit intomainfrom
release-please--branches--main--components--openfeature-sdk

Conversation

@openfeaturebot
Copy link
Contributor

🤖 I have created a release beep boop

0.6.0 (2026-03-05)

⚠ BREAKING CHANGES

  • add Ruby 4.0 support, require minimum Ruby 3.4 (#217)

Features

  • add Ruby 4.0 support, require minimum Ruby 3.4 (#217) (f38ba40)

This PR was generated with Release Please. See documentation.

Signed-off-by: OpenFeature Bot <109696520+openfeaturebot@users.noreply.github.com>
@gemini-code-assist
Copy link

Summary of Changes

Hello, 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.6.0 for the OpenFeature Ruby SDK. It updates all necessary version indicators and documentation to reflect the new release, which includes significant changes to Ruby version compatibility, specifically adding support for Ruby 4.0 and raising the minimum required Ruby version to 3.4.

Highlights

  • New Release: Version 0.6.0 of the OpenFeature Ruby SDK has been released.
  • Ruby Version Support: This release introduces support for Ruby 4.0 and now requires a minimum Ruby version of 3.4, which is a breaking change.
  • Automated Release: This pull request was automatically generated by Release Please to manage the release process.
Changelog
  • CHANGELOG.md
    • Added a new section for version 0.6.0.
    • Documented breaking changes related to Ruby 4.0 support and the new minimum Ruby 3.4 requirement.
    • Listed features, specifically the added Ruby 4.0 support.
Activity
  • This pull request was automatically created by the 'openfeaturebot' user via Release Please, indicating an automated release process.
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.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

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 contains routine updates for a new release, including version bumps in .release-please-manifest.json, CHANGELOG.md, Gemfile.lock, README.md, and lib/open_feature/sdk/version.rb. These changes are consistent with a version increment and do not introduce any functional code changes that require specific review comments.

@codecov
Copy link

codecov bot commented Mar 5, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.65%. Comparing base (f38ba40) to head (b920451).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #218   +/-   ##
=======================================
  Coverage   99.65%   99.65%           
=======================================
  Files          26       26           
  Lines         578      578           
=======================================
  Hits          576      576           
  Misses          2        2           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@josecolella josecolella merged commit 5776f4f into main Mar 5, 2026
15 checks passed
@josecolella josecolella deleted the release-please--branches--main--components--openfeature-sdk branch March 5, 2026 16:18
@openfeaturebot
Copy link
Contributor Author

🤖 Created releases:

🌻

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