chore(openfeature): pin mixpanel-ruby ~> 3.3 for fallback_reason (SDK-126) - #166
Merged
Conversation
…DK-126) DO NOT MERGE until mixpanel-ruby 3.3.0 is released. Bundler will refuse to resolve until then — that failure is the point. The wrapper's provider.rb dispatches on SelectedVariant#fallback_reason, which was introduced in the SDK-79 merge (PR #153). Both previously published mixpanel-ruby versions in the ~> 3.1 range (3.1.0, 3.2.0) lack that method, so an install pairing v0.1.0 of this gem with a pre-SDK-79 3.x mixpanel-ruby would raise NoMethodError on every evaluation past the existing rescue block. Bumping the constraint to ~> 3.3 (the next unreleased minor) forces the correct release sequencing: 1. This PR sits red on CI until mixpanel-ruby 3.3.0 ships with SDK-79 included. 2. Once mixpanel-ruby 3.3.0 is published, this PR's CI turns green and it can be merged + released as mixpanel-ruby-openfeature 0.2.0. Also bumps this gem's version 0.1.0 -> 0.2.0 (new capability surface) and adds a CHANGELOG entry.
Confidence Score: 5/5This looks safe to merge.
|
| Filename | Overview |
|---|---|
| openfeature-provider/mixpanel-ruby-openfeature.gemspec | Raises the runtime dependency from mixpanel-ruby ~> 3.1 to ~> 3.3. |
Reviews (4): Last reviewed commit: "Drop rationale comment above mixpanel-ru..." | Re-trigger Greptile
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #166 +/- ##
=======================================
Coverage 97.16% 97.16%
=======================================
Files 15 15
Lines 775 775
=======================================
Hits 753 753
Misses 22 22
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
The Ruby release-prep workflow (invoked separately per the Go/Ruby runbook pattern) generates CHANGELOG entries from conventional commit messages and bumps VERSION when the release is cut. Landing them manually in this PR pre-empts the workflow and duplicates work. Scope of this PR is now solely the gemspec pin bump (~> 3.1 → ~> 3.3). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
rahul-mixpanel
approved these changes
Jul 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bundler will refuse to resolve
mixpanel-ruby ~> 3.3until that version exists on RubyGems. That failure is the point of this PR — it enforces the correct two-step release sequencing.Summary
openfeature-provider/mixpanel-ruby-openfeature.gemspecruntime dep:~> 3.1→~> 3.3.mixpanel-ruby-openfeatureversion:0.1.0→0.2.0.openfeature/v0.2.0CHANGELOG entry.Why
The wrapper's
openfeature-provider/lib/mixpanel/openfeature/provider.rb:81dispatches onSelectedVariant#fallback_reason, which was introduced by the SDK-79 merge in #153. Both publishedmixpanel-rubyversions in the previous~> 3.1range —3.1.0and3.2.0— predate SDK-79 and lackfallback_reason. Any install that pairedmixpanel-ruby-openfeature 0.1.0with those would raiseNoMethodErroron every evaluation past the existingrescue StandardErrorblock. Greptile caught this on #153 immediately post-merge.Release sequencing
mixpanel-ruby ~> 3.3isn't published.mixpanel-ruby 3.3.0with the SDK-79 changes:lib/mixpanel-ruby/version.rb→3.3.0on masterrelease-rubygems.ymlworkflowmixpanel-ruby-openfeature 0.2.0.Verified locally
bundle installinopenfeature-provider/:Exactly the error CI should produce.
Linear: SDK-126