From 12e4858e6c67a9de5bc738f2df2b9ba70af67a05 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 19 Nov 2026 14:17:58 +0000 Subject: [PATCH] Version Packages (next) --- .changeset/pre.json | 7 +++++- packages/browser-sdk/CHANGELOG.md | 17 ++++++++++++++ packages/browser-sdk/package.json | 2 +- packages/cli/CHANGELOG.md | 7 ++++++ packages/cli/package.json | 2 +- packages/node-sdk/CHANGELOG.md | 18 +++++++++++++++ packages/node-sdk/package.json | 2 +- .../openfeature-node-provider/CHANGELOG.md | 18 +++++++++++++++ .../openfeature-node-provider/package.json | 2 +- packages/react-native-sdk/CHANGELOG.md | 22 +++++++++++++++++++ packages/react-native-sdk/package.json | 2 +- packages/react-sdk/CHANGELOG.md | 22 +++++++++++++++++++ packages/react-sdk/package.json | 2 +- packages/vue-sdk/CHANGELOG.md | 22 +++++++++++++++++++ packages/vue-sdk/package.json | 2 +- 15 files changed, 139 insertions(+), 8 deletions(-) create mode 100644 packages/cli/CHANGELOG.md diff --git a/.changeset/pre.json b/.changeset/pre.json index 6b485828..af0712b3 100644 --- a/.changeset/pre.json +++ b/.changeset/pre.json @@ -21,5 +21,10 @@ "@reflag/tsconfig": "0.0.2", "@reflag/vue-sdk": "2.0.0-next.0" }, - "changesets": [] + "changesets": [ + "browser-framework-collection-values", + "node-sdk-collection-values", + "react-native-collection-values", + "tidy-dependency-scanning" + ] } diff --git a/packages/browser-sdk/CHANGELOG.md b/packages/browser-sdk/CHANGELOG.md index 0dbef207..45870b79 100644 --- a/packages/browser-sdk/CHANGELOG.md +++ b/packages/browser-sdk/CHANGELOG.md @@ -1,5 +1,22 @@ # @reflag/browser-sdk +## 2.0.0-next.1 + +### Major Changes + +- 1716cae: Adopt protocol-v2, adding support for multivariate and JSON flags in Browser, React and Vue. + - Browser `getFlag()` and React `useFlag()` return direct values instead of flag wrappers. Vue `useFlag()` returns a ref to the direct value. Replace `.isEnabled` and `.config` access with direct values, using `.value` for Vue refs in script. + - Reads without a default return Booleans, using `false` when unavailable. Pass a positional default to read strings, numbers, arrays, or objects, with TypeScript inferring the return type. Missing values or values of a different top-level type use the default. Pass `null` to accept any JSON value, including null. Nested payload schemas are not validated at runtime. + - React and Vue's optional `Flags` registration checks non-null defaults against each flag's value type, including React Suspense reads. Named-interface and readonly defaults are supported across Browser, React and Vue without losing their inferred value types. + - React `useFlag()` never suspends. Replace `useFlag(key, { suspense: true })` with `useFlagSuspense(key)` to wait for initialization. Use `useIsLoading()` for loading state; existing provider and `useOptInFlags` Suspense options continue to control opt-in loading only. + - Flag reads automatically record checks. Replace flag-level `.track()` and `.requestFeedback()` calls with the client's separate methods or the framework's tracking and feedback hooks/composables. + - Browser `getFlags()` returns a record of direct values; unavailable flags may be `undefined`. Use `getFlagResults()` for diagnostic access without recording checks. + - Bootstrap data must come from Node SDK v2 and be consumed by matching v2 SDKs. Legacy v1 payloads are incompatible. Replace the Browser client's `bootstrappedFlags` option with `bootstrappedState` and pass the complete bootstrap payload. + - Overrides accept direct JSON values: `undefined` clears an override, while `null` is a value. Saved v1 caches and overrides are not reused. + - Bootstrapped clients load opt-in metadata when requested, without replacing server-provided flag values. Successful opt-in changes update both membership and flag values. + + The OpenFeature Browser provider continues to use Browser SDK v1. Legacy remote configuration is not automatically converted into multivariate flag values. + ## 1.7.4 ### Patch Changes diff --git a/packages/browser-sdk/package.json b/packages/browser-sdk/package.json index 226a8aec..90bb978a 100644 --- a/packages/browser-sdk/package.json +++ b/packages/browser-sdk/package.json @@ -1,6 +1,6 @@ { "name": "@reflag/browser-sdk", - "version": "2.0.0-next.0", + "version": "2.0.0-next.1", "license": "MIT", "repository": { "type": "git", diff --git a/packages/cli/CHANGELOG.md b/packages/cli/CHANGELOG.md new file mode 100644 index 00000000..e918990f --- /dev/null +++ b/packages/cli/CHANGELOG.md @@ -0,0 +1,7 @@ +# @reflag/cli + +## 1.0.5-next.0 + +### Patch Changes + +- 1adfced: Update Express and Zod to patched versions. Preserve CLI schema parsing behavior when migrating to Zod 4. diff --git a/packages/cli/package.json b/packages/cli/package.json index 21123fe2..00464bb4 100644 --- a/packages/cli/package.json +++ b/packages/cli/package.json @@ -1,6 +1,6 @@ { "name": "@reflag/cli", - "version": "1.0.4", + "version": "1.0.5-next.0", "description": "CLI for Reflag service", "homepage": "https://docs.reflag.com/", "license": "MIT", diff --git a/packages/node-sdk/CHANGELOG.md b/packages/node-sdk/CHANGELOG.md index 5e80c62c..4fde1df5 100644 --- a/packages/node-sdk/CHANGELOG.md +++ b/packages/node-sdk/CHANGELOG.md @@ -1,5 +1,23 @@ # @reflag/node-sdk +## 2.0.0-next.1 + +### Major Changes + +- 521de2f: Adopt protocol-v2, adding support for multivariate and JSON flags. + - `getFlag(context, key)` and bound `getFlag(key)` return direct values instead of flag wrappers. Reads without a default return Booleans, using `false` when unavailable. Replace `.isEnabled` and `.config` access with direct values. + - Pass a positional default to read strings, numbers, arrays, or objects. TypeScript infers the return type from the default without generated declarations. Missing values or values of a different top-level type use the default. Pass `null` to accept any JSON value, including null. Nested payload schemas are not validated at runtime. + - With optional `Flags` registration, TypeScript checks non-null defaults against each flag's value type for local, remote, and bound reads. Named-interface and readonly defaults are supported. + - Flag reads automatically record checks. Replace flag-level `.track()` calls with the client's separate `track()` API. + - `getFlags()` and `getFlagsRemote()` return records of direct values; unavailable flags may be `undefined`. + - `getFlagRemote(key, defaultValue, userId?, companyId?, context?)` now takes the default second, shifting existing user/company arguments one position to the right. Pass `undefined` for a Boolean read with explicit IDs. Bound clients use `getFlagRemote(key, defaultValue?)`. + - `getFlagDefinitions()` returns `{ flags, segments }` instead of an array. + - Saved fallback snapshots use a new format; v1 snapshots are not migrated automatically. Regenerate saved snapshots when upgrading. Built-in storage keeps v1 and v2 snapshots separate. + - `getFlagsForBootstrap()` produces protocol-v2 state. Upgrade Browser/framework consumers to compatible v2 SDKs before using this state; v1 bootstrap consumers are incompatible. + - Existing synchronization modes, bound contexts, and local overrides remain supported. Overrides and static fallbacks accept direct JSON values. + + The OpenFeature Node provider continues to use Node SDK v1. Legacy remote configuration is not automatically converted into multivariate flag values. + ## 1.8.3 ### Patch Changes diff --git a/packages/node-sdk/package.json b/packages/node-sdk/package.json index 770c8a20..fa945bf9 100644 --- a/packages/node-sdk/package.json +++ b/packages/node-sdk/package.json @@ -1,6 +1,6 @@ { "name": "@reflag/node-sdk", - "version": "2.0.0-next.0", + "version": "2.0.0-next.1", "license": "MIT", "repository": { "type": "git", diff --git a/packages/openfeature-node-provider/CHANGELOG.md b/packages/openfeature-node-provider/CHANGELOG.md index 8e2054b5..c4f53adc 100644 --- a/packages/openfeature-node-provider/CHANGELOG.md +++ b/packages/openfeature-node-provider/CHANGELOG.md @@ -1,5 +1,23 @@ # @reflag/openfeature-node-provider +## 1.2.9-next.0 + +### Patch Changes + +- 521de2f: Adopt protocol-v2, adding support for multivariate and JSON flags. + - `getFlag(context, key)` and bound `getFlag(key)` return direct values instead of flag wrappers. Reads without a default return Booleans, using `false` when unavailable. Replace `.isEnabled` and `.config` access with direct values. + - Pass a positional default to read strings, numbers, arrays, or objects. TypeScript infers the return type from the default without generated declarations. Missing values or values of a different top-level type use the default. Pass `null` to accept any JSON value, including null. Nested payload schemas are not validated at runtime. + - With optional `Flags` registration, TypeScript checks non-null defaults against each flag's value type for local, remote, and bound reads. Named-interface and readonly defaults are supported. + - Flag reads automatically record checks. Replace flag-level `.track()` calls with the client's separate `track()` API. + - `getFlags()` and `getFlagsRemote()` return records of direct values; unavailable flags may be `undefined`. + - `getFlagRemote(key, defaultValue, userId?, companyId?, context?)` now takes the default second, shifting existing user/company arguments one position to the right. Pass `undefined` for a Boolean read with explicit IDs. Bound clients use `getFlagRemote(key, defaultValue?)`. + - `getFlagDefinitions()` returns `{ flags, segments }` instead of an array. + - Saved fallback snapshots use a new format; v1 snapshots are not migrated automatically. Regenerate saved snapshots when upgrading. Built-in storage keeps v1 and v2 snapshots separate. + - `getFlagsForBootstrap()` produces protocol-v2 state. Upgrade Browser/framework consumers to compatible v2 SDKs before using this state; v1 bootstrap consumers are incompatible. + - Existing synchronization modes, bound contexts, and local overrides remain supported. Overrides and static fallbacks accept direct JSON values. + + The OpenFeature Node provider continues to use Node SDK v1. Legacy remote configuration is not automatically converted into multivariate flag values. + ## 1.2.8 ### Patch Changes diff --git a/packages/openfeature-node-provider/package.json b/packages/openfeature-node-provider/package.json index ff480955..adaf4648 100644 --- a/packages/openfeature-node-provider/package.json +++ b/packages/openfeature-node-provider/package.json @@ -1,6 +1,6 @@ { "name": "@reflag/openfeature-node-provider", - "version": "1.2.8", + "version": "1.2.9-next.0", "license": "MIT", "repository": { "type": "git", diff --git a/packages/react-native-sdk/CHANGELOG.md b/packages/react-native-sdk/CHANGELOG.md index 928a6e86..68cb8b21 100644 --- a/packages/react-native-sdk/CHANGELOG.md +++ b/packages/react-native-sdk/CHANGELOG.md @@ -1,5 +1,27 @@ # @reflag/react-native-sdk +## 2.0.0-next.1 + +### Major Changes + +- 1716cae: Adopt protocol-v2, adding support for multivariate and JSON flags in React Native. + - `useFlag()` returns direct values instead of flag wrappers. Reads without a default return Booleans, using `false` when unavailable. Replace `.isEnabled` and `.config` access with direct values. + - Pass a positional default to read strings, numbers, arrays, or objects, with TypeScript inferring the return type. Missing values or values of a different top-level type use the default. Pass `null` to accept any JSON value, including null. Nested payload schemas are not validated at runtime. + - `useFlag()` never suspends. Replace `useFlag(key, { suspense: true })` with `useFlagSuspense(key)` to wait for initialization, and use `useIsLoading()` for loading state. + - Flag reads automatically record checks. Replace flag-level tracking and feedback methods with `useTrack()` and `useSendFeedback()`, using your own Native feedback UI. + - Optional flag typing uses React's `Flags` registration in `@reflag/react-sdk`. Non-null defaults are checked against each registered flag's value type, and named-interface and readonly defaults are supported. Regenerate legacy wrapper-shaped declarations before upgrading. + - Bootstrap data must come from Node SDK v2. Pass the complete payload to `ReflagBootstrappedProvider`; legacy v1 payloads are incompatible. + - AsyncStorage persistence, native live updates and custom storage/SSE adapters remain supported. Live updates are enabled by default; the web toolbar and automatic feedback UI are disabled by default. + - Offline fallbacks accept direct JSON value maps. Arrays of enabled Boolean flag keys remain supported. + - Requires React 17 or later, compatible with your React Native runtime, and matching v2 React/Browser SDKs. + + Legacy wrapper and remote-config types are removed. Legacy remote configuration is not automatically converted into multivariate flag values. + +### Patch Changes + +- Updated dependencies [1716cae] + - @reflag/react-sdk@2.0.0-next.1 + ## 0.3.7 ### Patch Changes diff --git a/packages/react-native-sdk/package.json b/packages/react-native-sdk/package.json index 33abda8e..c8228fe6 100644 --- a/packages/react-native-sdk/package.json +++ b/packages/react-native-sdk/package.json @@ -1,6 +1,6 @@ { "name": "@reflag/react-native-sdk", - "version": "2.0.0-next.0", + "version": "2.0.0-next.1", "license": "MIT", "repository": { "type": "git", diff --git a/packages/react-sdk/CHANGELOG.md b/packages/react-sdk/CHANGELOG.md index 730983d3..80099093 100644 --- a/packages/react-sdk/CHANGELOG.md +++ b/packages/react-sdk/CHANGELOG.md @@ -1,5 +1,27 @@ # @reflag/react-sdk +## 2.0.0-next.1 + +### Major Changes + +- 1716cae: Adopt protocol-v2, adding support for multivariate and JSON flags in Browser, React and Vue. + - Browser `getFlag()` and React `useFlag()` return direct values instead of flag wrappers. Vue `useFlag()` returns a ref to the direct value. Replace `.isEnabled` and `.config` access with direct values, using `.value` for Vue refs in script. + - Reads without a default return Booleans, using `false` when unavailable. Pass a positional default to read strings, numbers, arrays, or objects, with TypeScript inferring the return type. Missing values or values of a different top-level type use the default. Pass `null` to accept any JSON value, including null. Nested payload schemas are not validated at runtime. + - React and Vue's optional `Flags` registration checks non-null defaults against each flag's value type, including React Suspense reads. Named-interface and readonly defaults are supported across Browser, React and Vue without losing their inferred value types. + - React `useFlag()` never suspends. Replace `useFlag(key, { suspense: true })` with `useFlagSuspense(key)` to wait for initialization. Use `useIsLoading()` for loading state; existing provider and `useOptInFlags` Suspense options continue to control opt-in loading only. + - Flag reads automatically record checks. Replace flag-level `.track()` and `.requestFeedback()` calls with the client's separate methods or the framework's tracking and feedback hooks/composables. + - Browser `getFlags()` returns a record of direct values; unavailable flags may be `undefined`. Use `getFlagResults()` for diagnostic access without recording checks. + - Bootstrap data must come from Node SDK v2 and be consumed by matching v2 SDKs. Legacy v1 payloads are incompatible. Replace the Browser client's `bootstrappedFlags` option with `bootstrappedState` and pass the complete bootstrap payload. + - Overrides accept direct JSON values: `undefined` clears an override, while `null` is a value. Saved v1 caches and overrides are not reused. + - Bootstrapped clients load opt-in metadata when requested, without replacing server-provided flag values. Successful opt-in changes update both membership and flag values. + + The OpenFeature Browser provider continues to use Browser SDK v1. Legacy remote configuration is not automatically converted into multivariate flag values. + +### Patch Changes + +- Updated dependencies [1716cae] + - @reflag/browser-sdk@2.0.0-next.1 + ## 1.7.4 ### Patch Changes diff --git a/packages/react-sdk/package.json b/packages/react-sdk/package.json index 10c10057..a0cb1abb 100644 --- a/packages/react-sdk/package.json +++ b/packages/react-sdk/package.json @@ -1,6 +1,6 @@ { "name": "@reflag/react-sdk", - "version": "2.0.0-next.0", + "version": "2.0.0-next.1", "license": "MIT", "repository": { "type": "git", diff --git a/packages/vue-sdk/CHANGELOG.md b/packages/vue-sdk/CHANGELOG.md index 46aa5763..2492d1ba 100644 --- a/packages/vue-sdk/CHANGELOG.md +++ b/packages/vue-sdk/CHANGELOG.md @@ -1,5 +1,27 @@ # @reflag/vue-sdk +## 2.0.0-next.1 + +### Major Changes + +- 1716cae: Adopt protocol-v2, adding support for multivariate and JSON flags in Browser, React and Vue. + - Browser `getFlag()` and React `useFlag()` return direct values instead of flag wrappers. Vue `useFlag()` returns a ref to the direct value. Replace `.isEnabled` and `.config` access with direct values, using `.value` for Vue refs in script. + - Reads without a default return Booleans, using `false` when unavailable. Pass a positional default to read strings, numbers, arrays, or objects, with TypeScript inferring the return type. Missing values or values of a different top-level type use the default. Pass `null` to accept any JSON value, including null. Nested payload schemas are not validated at runtime. + - React and Vue's optional `Flags` registration checks non-null defaults against each flag's value type, including React Suspense reads. Named-interface and readonly defaults are supported across Browser, React and Vue without losing their inferred value types. + - React `useFlag()` never suspends. Replace `useFlag(key, { suspense: true })` with `useFlagSuspense(key)` to wait for initialization. Use `useIsLoading()` for loading state; existing provider and `useOptInFlags` Suspense options continue to control opt-in loading only. + - Flag reads automatically record checks. Replace flag-level `.track()` and `.requestFeedback()` calls with the client's separate methods or the framework's tracking and feedback hooks/composables. + - Browser `getFlags()` returns a record of direct values; unavailable flags may be `undefined`. Use `getFlagResults()` for diagnostic access without recording checks. + - Bootstrap data must come from Node SDK v2 and be consumed by matching v2 SDKs. Legacy v1 payloads are incompatible. Replace the Browser client's `bootstrappedFlags` option with `bootstrappedState` and pass the complete bootstrap payload. + - Overrides accept direct JSON values: `undefined` clears an override, while `null` is a value. Saved v1 caches and overrides are not reused. + - Bootstrapped clients load opt-in metadata when requested, without replacing server-provided flag values. Successful opt-in changes update both membership and flag values. + + The OpenFeature Browser provider continues to use Browser SDK v1. Legacy remote configuration is not automatically converted into multivariate flag values. + +### Patch Changes + +- Updated dependencies [1716cae] + - @reflag/browser-sdk@2.0.0-next.1 + ## 1.5.7 ### Patch Changes diff --git a/packages/vue-sdk/package.json b/packages/vue-sdk/package.json index 13149aba..f76a71ac 100644 --- a/packages/vue-sdk/package.json +++ b/packages/vue-sdk/package.json @@ -1,6 +1,6 @@ { "name": "@reflag/vue-sdk", - "version": "2.0.0-next.0", + "version": "2.0.0-next.1", "license": "MIT", "repository": { "type": "git",