Skip to content

Version Packages (next) - #796

Open
roncohen wants to merge 1 commit into
mainfrom
changeset-release/main
Open

roncohen wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@roncohen

@roncohen roncohen commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

main is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on main.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@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.

@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.

@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

@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

@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

@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.

@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.

Copilot AI balanced review requested due to automatic review settings November 6, 2026 07:50

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No active review issues block the CLI 1.0.5 version bump and release-note updates.

No open issues 🎉

What changed in this PR

Prepares the @reflag/cli 1.0.5 patch release, documenting previously implemented Express and Zod updates and preserved schema parsing behavior.

Changes:

  • Bumps the CLI package version from 1.0.4 to 1.0.5.
  • Adds release notes and removes the consumed changeset.
File Description
packages/​cli/​package.json Updates the package version to 1.0.5.
packages/​cli/​CHANGELOG.md Records dependency updates and Zod 4 compatibility work.
.changeset/​tidy-dependency-scanning.md Removes the changeset incorporated into the release notes.

Review effort: Balanced

@roncohen
roncohen force-pushed the changeset-release/main branch from 584a7a3 to 9ae3ca7 Compare November 18, 2026 15:05

@reflag-review reflag-review Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Risk: medium

no actionable findings

@reflag-review reflag-review Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Risk: medium

no actionable findings

@roncohen
roncohen force-pushed the changeset-release/main branch from a2f9e05 to 0ac0ae2 Compare November 19, 2026 11:15

@reflag-review reflag-review Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Risk: medium

no actionable findings

@roncohen roncohen changed the title Version Packages Version Packages (next) Nov 19, 2026
@roncohen
roncohen force-pushed the changeset-release/main branch from 0ac0ae2 to 12e4858 Compare November 19, 2026 14:18

@reflag-review reflag-review Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Risk: low

no actionable findings

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants