fix: Ensure FDv2 waits for network results instead of cached results.#1397
Conversation
|
@launchdarkly/js-sdk-common size report |
|
@launchdarkly/js-client-sdk size report |
|
@launchdarkly/browser size report |
|
@launchdarkly/js-client-sdk-common size report |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit fa52d3a. Configure here.
🤖 I have created a release *beep* *boop* --- <details><summary>browser: 0.1.24</summary> ## [0.1.24](browser-v0.1.23...browser-v0.1.24) (2026-05-28) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-client-sdk bumped from 4.7.2 to 4.7.3 </details> <details><summary>js-client-sdk: 4.7.3</summary> ## [4.7.3](js-client-sdk-v4.7.2...js-client-sdk-v4.7.3) (2026-05-28) ### Bug Fixes * Ensure FDv2 waits for network results instead of cached results. ([#1397](#1397)) ([142da36](142da36)) </details> <details><summary>react-sdk: 4.0.5</summary> ## [4.0.5](react-sdk-v4.0.4...react-sdk-v4.0.5) (2026-05-28) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-client-sdk bumped from ^4.7.2 to ^4.7.3 </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > No application logic in the diff—only version numbers, changelogs, and dependency pins from automated release tooling. > > **Overview** > Release Please version bump for **@launchdarkly/js-client-sdk** **4.7.3**, with changelog noting the shipped fix that **FDv2 waits for network results instead of cached results** ([#1397](#1397)). The diff itself is release metadata: `.release-please-manifest.json`, package versions, changelogs, example app dependency pins, and embedded SDK version strings in `BrowserInfo` and the React client default `wrapperVersion`. > > **@launchdarkly/browser** **0.1.24** and **@launchdarkly/react-sdk** **4.0.5** are dependency-only releases that pick up **js-client-sdk** **4.7.3**; React examples and combined-browser likewise update their pinned versions. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 9282971. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY --> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Note
Low Risk
Single-path behavior change in browser identify options; aligns with documented browser-only network semantics and does not touch auth or persistence.
Overview
The browser client’s
identifyResultpath now always passeswaitForNetworkResults: trueinto the shared identify flow so FDv2 identify completes on fresh network flag data instead of settling on cached results.The identify options object is typed as
LDBaseIdentifyOptions, and whensheddableis already provided the code copies options with a spread (same as the default branch) before settingwaitForNetworkResults.Reviewed by Cursor Bugbot for commit 4f086c7. Bugbot is set up for automated code reviews on this repo. Configure here.