chore(openfeature): pin mixpanel ^0.22.0 for fallback_reason (SDK-126)#284
Draft
tylerjroach wants to merge 1 commit into
Draft
Conversation
MixpanelProvider now dereferences `variant.fallback_reason` (added by #277 / SDK-79). The current peerDep `mixpanel: ^0.21.0` resolves to `>=0.21.0 <0.22.0` — the only published version in that range (0.21.0) predates SDK-79 and does NOT expose that field, so the wrapper falls into its legacy sentinel branch and can't surface the specific fallback reason. Bump peerDep to `^0.22.0` (`>=0.22.0 <0.23.0`). npm will refuse to resolve the wrapper against pre-0.22.0 mixpanel installs, matching what the code actually needs. CI will remain blocked until mixpanel 0.22.0 is published on npm. That's intentional — same release-sequencing pattern as mixpanel/mixpanel-ruby#166. Also bump wrapper version 0.1.0 -> 0.2.0 (new capability surface). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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
1 participant
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.
Summary
Follow-up to SDK-79.
packages/openfeature-server-provider/src/MixpanelProvider.tsnow dereferencesvariant.fallback_reason(added by #277). The peerDepmixpanel: ^0.21.0still allows resolving against the only currently-published mixpanel version (0.21.0), which predates SDK-79 — so the wrapper falls through to its legacy sentinel branch and can never surface the specific fallback reason.Changes
packages/openfeature-server-provider/package.json: bumpmixpanel: ^0.21.0→^0.22.0(npm caret on 0.x →>=0.22.0 <0.23.0, excludes 0.21.0)packages/openfeature-server-provider/package.json: bump wrapper version0.1.0→0.2.0Merge sequencing
CI is expected to fail until mixpanel 0.22.0 is published on npm. That failure is the point:
Same pattern as mixpanel/mixpanel-ruby#166 and mixpanel/mixpanel-python#185.
Test plan
Refs: SDK-126, SDK-79
🤖 Generated with Claude Code