Repository navigation
Conversation
Contributor
There was a problem hiding this comment.
🟢 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
force-pushed
the
changeset-release/main
branch
from
November 18, 2026 15:05
584a7a3 to
9ae3ca7
Compare
roncohen
force-pushed
the
changeset-release/main
branch
from
November 19, 2026 10:46
9ae3ca7 to
a2f9e05
Compare
roncohen
force-pushed
the
changeset-release/main
branch
from
November 19, 2026 11:15
a2f9e05 to
0ac0ae2
Compare
roncohen
force-pushed
the
changeset-release/main
branch
from
November 19, 2026 14:18
0ac0ae2 to
12e4858
Compare
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
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.
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.
mainis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmain.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.
getFlag()and ReactuseFlag()return direct values instead of flag wrappers. VueuseFlag()returns a ref to the direct value. Replace.isEnabledand.configaccess with direct values, using.valuefor Vue refs in script.falsewhen 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. Passnullto accept any JSON value, including null. Nested payload schemas are not validated at runtime.Flagsregistration 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.useFlag()never suspends. ReplaceuseFlag(key, { suspense: true })withuseFlagSuspense(key)to wait for initialization. UseuseIsLoading()for loading state; existing provider anduseOptInFlagsSuspense options continue to control opt-in loading only..track()and.requestFeedback()calls with the client's separate methods or the framework's tracking and feedback hooks/composables.getFlags()returns a record of direct values; unavailable flags may beundefined. UsegetFlagResults()for diagnostic access without recording checks.bootstrappedFlagsoption withbootstrappedStateand pass the complete bootstrap payload.undefinedclears an override, whilenullis a value. Saved v1 caches and overrides are not reused.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 boundgetFlag(key)return direct values instead of flag wrappers. Reads without a default return Booleans, usingfalsewhen unavailable. Replace.isEnabledand.configaccess with direct values.nullto accept any JSON value, including null. Nested payload schemas are not validated at runtime.Flagsregistration, TypeScript checks non-null defaults against each flag's value type for local, remote, and bound reads. Named-interface and readonly defaults are supported..track()calls with the client's separatetrack()API.getFlags()andgetFlagsRemote()return records of direct values; unavailable flags may beundefined.getFlagRemote(key, defaultValue, userId?, companyId?, context?)now takes the default second, shifting existing user/company arguments one position to the right. Passundefinedfor a Boolean read with explicit IDs. Bound clients usegetFlagRemote(key, defaultValue?).getFlagDefinitions()returns{ flags, segments }instead of an array.getFlagsForBootstrap()produces protocol-v2 state. Upgrade Browser/framework consumers to compatible v2 SDKs before using this state; v1 bootstrap consumers are incompatible.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, usingfalsewhen unavailable. Replace.isEnabledand.configaccess with direct values.nullto accept any JSON value, including null. Nested payload schemas are not validated at runtime.useFlag()never suspends. ReplaceuseFlag(key, { suspense: true })withuseFlagSuspense(key)to wait for initialization, and useuseIsLoading()for loading state.useTrack()anduseSendFeedback(), using your own Native feedback UI.Flagsregistration 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.ReflagBootstrappedProvider; legacy v1 payloads are incompatible.Legacy wrapper and remote-config types are removed. Legacy remote configuration is not automatically converted into multivariate flag values.
Patch Changes
@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.
getFlag()and ReactuseFlag()return direct values instead of flag wrappers. VueuseFlag()returns a ref to the direct value. Replace.isEnabledand.configaccess with direct values, using.valuefor Vue refs in script.falsewhen 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. Passnullto accept any JSON value, including null. Nested payload schemas are not validated at runtime.Flagsregistration 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.useFlag()never suspends. ReplaceuseFlag(key, { suspense: true })withuseFlagSuspense(key)to wait for initialization. UseuseIsLoading()for loading state; existing provider anduseOptInFlagsSuspense options continue to control opt-in loading only..track()and.requestFeedback()calls with the client's separate methods or the framework's tracking and feedback hooks/composables.getFlags()returns a record of direct values; unavailable flags may beundefined. UsegetFlagResults()for diagnostic access without recording checks.bootstrappedFlagsoption withbootstrappedStateand pass the complete bootstrap payload.undefinedclears an override, whilenullis a value. Saved v1 caches and overrides are not reused.The OpenFeature Browser provider continues to use Browser SDK v1. Legacy remote configuration is not automatically converted into multivariate flag values.
Patch Changes
@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.
getFlag()and ReactuseFlag()return direct values instead of flag wrappers. VueuseFlag()returns a ref to the direct value. Replace.isEnabledand.configaccess with direct values, using.valuefor Vue refs in script.falsewhen 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. Passnullto accept any JSON value, including null. Nested payload schemas are not validated at runtime.Flagsregistration 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.useFlag()never suspends. ReplaceuseFlag(key, { suspense: true })withuseFlagSuspense(key)to wait for initialization. UseuseIsLoading()for loading state; existing provider anduseOptInFlagsSuspense options continue to control opt-in loading only..track()and.requestFeedback()calls with the client's separate methods or the framework's tracking and feedback hooks/composables.getFlags()returns a record of direct values; unavailable flags may beundefined. UsegetFlagResults()for diagnostic access without recording checks.bootstrappedFlagsoption withbootstrappedStateand pass the complete bootstrap payload.undefinedclears an override, whilenullis a value. Saved v1 caches and overrides are not reused.The OpenFeature Browser provider continues to use Browser SDK v1. Legacy remote configuration is not automatically converted into multivariate flag values.
Patch Changes
@reflag/cli@1.0.5-next.0
Patch Changes
@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 boundgetFlag(key)return direct values instead of flag wrappers. Reads without a default return Booleans, usingfalsewhen unavailable. Replace.isEnabledand.configaccess with direct values.nullto accept any JSON value, including null. Nested payload schemas are not validated at runtime.Flagsregistration, TypeScript checks non-null defaults against each flag's value type for local, remote, and bound reads. Named-interface and readonly defaults are supported..track()calls with the client's separatetrack()API.getFlags()andgetFlagsRemote()return records of direct values; unavailable flags may beundefined.getFlagRemote(key, defaultValue, userId?, companyId?, context?)now takes the default second, shifting existing user/company arguments one position to the right. Passundefinedfor a Boolean read with explicit IDs. Bound clients usegetFlagRemote(key, defaultValue?).getFlagDefinitions()returns{ flags, segments }instead of an array.getFlagsForBootstrap()produces protocol-v2 state. Upgrade Browser/framework consumers to compatible v2 SDKs before using this state; v1 bootstrap consumers are incompatible.The OpenFeature Node provider continues to use Node SDK v1. Legacy remote configuration is not automatically converted into multivariate flag values.