chore(openfeature): pin mixpanel ^0.23.0 for fallback_reason (SDK-126) - #284
Merged
tylerjroach merged 1 commit intoJul 29, 2026
Conversation
MixpanelProvider dereferences variant.fallback_reason, which was added by #277 (SDK-79) and first published in mixpanel 0.23.0 — not 0.22.0 (that release was only the monorepo split). The previous peerDep ^0.21.0 allowed resolving against SDKs that predate fallback_reason, so the provider fell through to its legacy sentinel branch and could never surface the specific fallback reason. Note that npm caret ranges on 0.x are minor-locked: ^0.22.0 resolves to >=0.22.0 <0.23.0, which would have excluded the only release that actually carries the field. ^0.23.0 is required. Also refreshes the lockfile's stale packages/mixpanel version (0.22.0 -> 0.23.0) left over from the 0.23.0 release prep. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
tylerjroach
force-pushed
the
tylerroach-sdk-126-node-openfeature-pin-mixpanel-to-sdk-79-release
branch
from
July 29, 2026 20:06
4619433 to
3ca7637
Compare
tylerjroach
changed the title
tylerjroach
marked this pull request as ready for review
July 29, 2026 20:17
efahk
approved these changes
Jul 29, 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
2 participants
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
packages/openfeature-server-provider/src/MixpanelProvider.tsdereferencesvariant.fallback_reason, added by #277 (SDK-79). That field first shipped in mixpanel 0.23.0 — 0.22.0 was only the monorepo split and does not contain it.The peerDep
mixpanel: ^0.21.0allowed resolving against SDKs that predatefallback_reason, so the provider fell through to its legacy sentinel branch (MixpanelProvider.ts:279) and could never surface the specific fallback reason.Changes
packages/openfeature-server-provider/package.json: bump peerDepmixpanel: ^0.21.0→^0.23.0package-lock.json: mirror the peerDep, and refresh the stalepackages/mixpanelversion (0.22.0→0.23.0) left over from the 0.23.0 release prep in release: prepare analytics 0.23.0 #288Why
^0.23.0and not^0.22.0: npm caret ranges on0.xare minor-locked, so^0.22.0resolves to>=0.22.0 <0.23.0— it would have pinned to the one release lacking the field while excluding the release that has it.Release status
mixpanel
0.23.0is already published (lateston npm), so no merge sequencing is needed and CI should pass on this branch as-is.The wrapper version stays at
0.1.0; the release-prep workflow owns that bump.Test plan
npm cisucceeds with the updated lockfile (CI usesnpm ci)npm testgreen — 278 mixpanel + 56 openfeature-server-provider tests passMixpanelProvider.tsnow that the peerDep excludes pre-SDK-79 mixpanelRefs: SDK-126, SDK-79
🤖 Generated with Claude Code