-
Notifications
You must be signed in to change notification settings - Fork 31
feat!: release js-client-sdk v4 #1093
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm removing this directory as the LD docs should have the migration docs available.
|
@launchdarkly/js-sdk-common size report |
|
@launchdarkly/browser size report |
|
@launchdarkly/js-client-sdk size report |
|
@launchdarkly/js-client-sdk-common size report |
🤖 I have created a release *beep* *boop* --- <details><summary>browser: 0.1.4</summary> ## [0.1.4](browser-v0.1.3...browser-v0.1.4) (2026-02-04) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-client-sdk bumped from 0.13.1 to 4.0.0 </details> <details><summary>browser-telemetry: 1.0.20</summary> ## [1.0.20](browser-telemetry-v1.0.19...browser-telemetry-v1.0.20) (2026-02-04) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/js-client-sdk bumped from 0.13.1 to 4.0.0 </details> <details><summary>js-client-sdk: 4.0.0</summary> ## [4.0.0](js-client-sdk-v0.13.1...js-client-sdk-v4.0.0) (2026-02-04) ### ⚠ BREAKING CHANGES * release js-client-sdk v4 ([#1093](#1093)) ### Features * release js-client-sdk v4 ([#1093](#1093)) ([1457793](1457793)) </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] > **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-sdk` v4.0.0** (marked as a *breaking change*) and updates its embedded version string used in `BrowserInfo`. > > Bumps release metadata and dependent package versions to match: `@launchdarkly/browser` to `0.1.4` (now depends on `@launchdarkly/js-client-sdk@4.0.0`) and `@launchdarkly/browser-telemetry` to `1.0.20` (devDependency bump), with corresponding changelog entries and `.release-please-manifest.json` updates. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 7a2fbed. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY --> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Note
Low Risk
Docs and release automation config changes only; no runtime code paths are modified, but the
release-as: 4.0.0setting will affect publishing/versioning.Overview
Updates the browser SDK package metadata for the
@launchdarkly/js-client-sdkv4 release by removing the alpha/CAUTION notice frompackages/sdk/browser/README.md.Removes the
packages/sdk/browser/upgradev4 upgrade guide docs, and pins automated releases forpackages/sdk/browserto4.0.0viarelease-please-config.json(replacing the previous pre-major minor bump behavior).Written by Cursor Bugbot for commit 6e3fa5f. This will update automatically on new commits. Configure here.