chore(main): release openfeature-meta_provider 0.0.8#103
chore(main): release openfeature-meta_provider 0.0.8#103openfeaturebot wants to merge 2 commits intomainfrom
Conversation
Summary of ChangesHello, 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 performs a release of the Highlights
Changelog
Activity
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
Code Review
This pull request, generated by Release Please, is intended to release version 0.0.8. However, the current version in the source files on the base branch appears to be 0.1.0. This PR downgrades the version from 0.1.0 to 0.0.8 in lib/openfeature/meta_provider_version.rb and Gemfile.lock. Downgrading a version number is a critical issue as it violates semantic versioning and can cause significant problems for consumers of this gem. It seems there's an inconsistency between the version tracked by release-please in .release-please-manifest.json (which was 0.0.7) and the version present in the code (0.1.0). This underlying inconsistency should be resolved before this release can proceed.
| remote: . | ||
| specs: | ||
| openfeature-meta_provider (0.1.0) | ||
| openfeature-meta_provider (0.0.8) |
1ad26fc to
a126639
Compare
josecolella
left a comment
There was a problem hiding this comment.
LGTM - CI passing, release PR looks good.
Signed-off-by: OpenFeature Bot <109696520+openfeaturebot@users.noreply.github.com>
a126639 to
97c6103
Compare
josecolella
left a comment
There was a problem hiding this comment.
Approved release PR
Take newer versions for both meta_provider (0.0.8) and flipt-provider (0.0.4). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Jose Colella <jose.colella@gusto.com>
|
The version downgrade flagged by @gemini-code-assist is correct — the manifest was out of sync with the actual version on main ( Fixed the root cause in #113 by updating the manifest to 🤖 Jose's AI agent |
Pull request was closed
## Summary - The release-please manifest tracked `meta_provider` as `0.0.7`, but the actual version on main is `0.1.0` (set in commit 9cce3f4) - This mismatch caused release-please to generate PR #103 which would **downgrade** the version from `0.1.0` to `0.0.8` - Fixes the manifest to `0.1.0` so release-please generates correct version bumps going forward ## Follow-up After this merges, close PR #103 and let release-please regenerate it with the correct next version. *🤖 Jose's AI agent* Signed-off-by: Jose Colella <jose.colella@gusto.com> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
🤖 I have created a release beep boop
0.0.8 (2026-03-18)
✨ New Features
🧹 Chore
This PR was generated with Release Please. See documentation.