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.
🤖 I have created a release beep boop
browser: 0.1.4
0.1.4 (2026-02-04)
Dependencies
browser-telemetry: 1.0.20
1.0.20 (2026-02-04)
Dependencies
js-client-sdk: 4.0.0
4.0.0 (2026-02-04)
⚠ BREAKING CHANGES
Features
This PR was generated with Release Please. See documentation.
Note
Medium Risk
Primarily a release/versioning PR, but it promotes a browser SDK to a new major version and updates downstream packages, which can introduce breaking API/behavior changes for consumers.
Overview
Publishes
@launchdarkly/js-client-sdkv4.0.0 (marked as a breaking change) and updates its embedded version string used inBrowserInfo.Bumps release metadata and dependent package versions to match:
@launchdarkly/browserto0.1.4(now depends on@launchdarkly/js-client-sdk@4.0.0) and@launchdarkly/browser-telemetryto1.0.20(devDependency bump), with corresponding changelog entries and.release-please-manifest.jsonupdates.Written by Cursor Bugbot for commit 7a2fbed. This will update automatically on new commits. Configure here.