From 190c1b69fb9c453e2a43960ff9d56ef5030debd1 Mon Sep 17 00:00:00 2001 From: Tyler Roach Date: Tue, 21 Jul 2026 13:49:00 -0400 Subject: [PATCH] chore(openfeature): pin mixpanel ^0.22.0 for fallback_reason (SDK-126) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 --- packages/openfeature-server-provider/package.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/packages/openfeature-server-provider/package.json b/packages/openfeature-server-provider/package.json index 34be978..8b5c56f 100644 --- a/packages/openfeature-server-provider/package.json +++ b/packages/openfeature-server-provider/package.json @@ -1,6 +1,6 @@ { "name": "@mixpanel/openfeature-server-provider", - "version": "0.1.0", + "version": "0.2.0", "description": "OpenFeature server provider for Mixpanel feature flags", "main": "dist/index.js", "types": "dist/index.d.ts", @@ -14,7 +14,7 @@ }, "peerDependencies": { "@openfeature/server-sdk": "^1.17.0", - "mixpanel": "^0.21.0" + "mixpanel": "^0.22.0" }, "devDependencies": { "@openfeature/core": "^1.9.2",