fix!: updating to major version 1 #1089
Merged
+1
−1
Conversation
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
kinyoklion
approved these changes
Feb 3, 2026
Merged
joker23
pushed a commit
that referenced
this pull request
Feb 4, 2026
🤖 I have created a release *beep* *boop* --- <details><summary>akamai-edgeworker-sdk-common: 2.0.13</summary> ## [2.0.13](akamai-edgeworker-sdk-common-v2.0.12...akamai-edgeworker-sdk-common-v2.0.13) (2026-02-03) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from ^2.17.1 to ^2.17.2 </details> <details><summary>akamai-server-base-sdk: 3.0.14</summary> ## [3.0.14](akamai-server-base-sdk-v3.0.13...akamai-server-base-sdk-v3.0.14) (2026-02-03) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/akamai-edgeworker-sdk-common bumped from ^2.0.12 to ^2.0.13 * @launchdarkly/js-server-sdk-common bumped from ^2.17.1 to ^2.17.2 </details> <details><summary>akamai-server-edgekv-sdk: 1.4.16</summary> ## [1.4.16](akamai-server-edgekv-sdk-v1.4.15...akamai-server-edgekv-sdk-v1.4.16) (2026-02-03) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/akamai-edgeworker-sdk-common bumped from ^2.0.12 to ^2.0.13 * @launchdarkly/js-server-sdk-common bumped from ^2.17.1 to ^2.17.2 </details> <details><summary>cloudflare-server-sdk: 2.7.13</summary> ## [2.7.13](cloudflare-server-sdk-v2.7.12...cloudflare-server-sdk-v2.7.13) (2026-02-03) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common-edge bumped from 2.6.11 to 2.6.12 </details> <details><summary>fastly-server-sdk: 0.2.5</summary> ## [0.2.5](fastly-server-sdk-v0.2.4...fastly-server-sdk-v0.2.5) (2026-02-03) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from 2.17.1 to 2.17.2 </details> <details><summary>jest: 1.0.0</summary> ## [1.0.0](jest-v0.2.2...jest-v1.0.0) (2026-02-03) ### ⚠ BREAKING CHANGES * updating to major version 1 ([#1089](#1089)) ### Bug Fixes * updating to major version 1 ([#1089](#1089)) ([4c194d8](4c194d8)) </details> <details><summary>js-server-sdk-common: 2.17.2</summary> ## [2.17.2](js-server-sdk-common-v2.17.1...js-server-sdk-common-v2.17.2) (2026-02-03) ### Bug Fixes * **node-server-sdk:** No FDv1 fallback when using custom datasystem ([#1088](#1088)) ([5111112](5111112)) </details> <details><summary>js-server-sdk-common-edge: 2.6.12</summary> ## [2.6.12](js-server-sdk-common-edge-v2.6.11...js-server-sdk-common-edge-v2.6.12) (2026-02-03) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from 2.17.1 to 2.17.2 </details> <details><summary>node-server-sdk: 9.10.6</summary> ## [9.10.6](node-server-sdk-v9.10.5...node-server-sdk-v9.10.6) (2026-02-03) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from 2.17.1 to 2.17.2 </details> <details><summary>node-server-sdk-dynamodb: 6.2.18</summary> ## [6.2.18](node-server-sdk-dynamodb-v6.2.17...node-server-sdk-dynamodb-v6.2.18) (2026-02-03) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/node-server-sdk bumped from 9.10.5 to 9.10.6 * peerDependencies * @launchdarkly/node-server-sdk bumped from >=9.4.3 to >=9.10.6 </details> <details><summary>node-server-sdk-otel: 1.3.6</summary> ## [1.3.6](node-server-sdk-otel-v1.3.5...node-server-sdk-otel-v1.3.6) (2026-02-03) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/node-server-sdk bumped from 9.10.5 to 9.10.6 * peerDependencies * @launchdarkly/node-server-sdk bumped from >=9.4.3 to >=9.10.6 </details> <details><summary>node-server-sdk-redis: 4.2.18</summary> ## [4.2.18](node-server-sdk-redis-v4.2.17...node-server-sdk-redis-v4.2.18) (2026-02-03) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/node-server-sdk bumped from 9.10.5 to 9.10.6 * peerDependencies * @launchdarkly/node-server-sdk bumped from >=9.4.3 to >=9.10.6 </details> <details><summary>server-sdk-ai: 0.16.1</summary> ## [0.16.1](server-sdk-ai-v0.16.0...server-sdk-ai-v0.16.1) (2026-02-03) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/js-server-sdk-common bumped from 2.17.1 to 2.17.2 * peerDependencies * @launchdarkly/js-server-sdk-common bumped from 2.x to 2.17.2 </details> <details><summary>server-sdk-ai-langchain: 0.4.4</summary> ## [0.4.4](server-sdk-ai-langchain-v0.4.3...server-sdk-ai-langchain-v0.4.4) (2026-02-03) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/server-sdk-ai bumped from ^0.16.0 to ^0.16.1 * peerDependencies * @launchdarkly/server-sdk-ai bumped from ^0.15.0 to ^0.16.1 </details> <details><summary>server-sdk-ai-openai: 0.4.4</summary> ## [0.4.4](server-sdk-ai-openai-v0.4.3...server-sdk-ai-openai-v0.4.4) (2026-02-03) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/js-server-sdk-common bumped from 2.17.1 to 2.17.2 * @launchdarkly/server-sdk-ai bumped from ^0.16.0 to ^0.16.1 * peerDependencies * @launchdarkly/server-sdk-ai bumped from ^0.15.0 to ^0.16.1 </details> <details><summary>server-sdk-ai-vercel: 0.4.4</summary> ## [0.4.4](server-sdk-ai-vercel-v0.4.3...server-sdk-ai-vercel-v0.4.4) (2026-02-03) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/server-sdk-ai bumped from ^0.16.0 to ^0.16.1 * peerDependencies * @launchdarkly/server-sdk-ai bumped from ^0.15.0 to ^0.16.1 </details> <details><summary>shopify-oxygen-sdk: 0.1.3</summary> ## [0.1.3](shopify-oxygen-sdk-v0.1.2...shopify-oxygen-sdk-v0.1.3) (2026-02-03) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from 2.17.1 to 2.17.2 </details> <details><summary>vercel-server-sdk: 1.3.38</summary> ## [1.3.38](vercel-server-sdk-v1.3.37...vercel-server-sdk-v1.3.38) (2026-02-03) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common-edge bumped from 2.6.11 to 2.6.12 </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** > Mostly automated version/changelog updates, but it ships a bug-fix update to shared server SDK common code and includes a major-version bump of `@launchdarkly/jest`, which could affect downstream consumers. > > **Overview** > This PR is a release-please publish/update across the monorepo, updating `.release-please-manifest.json`, package versions, and changelogs for AI providers, edge/server SDKs, feature-store integrations, and tooling. > > Most changes are dependency/version propagation (including updating embedded `sdkVersion` constants in platform info) to pick up `@launchdarkly/js-server-sdk-common` `2.17.2` (noted bug fix: no FDv1 fallback with a custom datasystem) and `js-server-sdk-common-edge` `2.6.12`, plus bumps to `@launchdarkly/server-sdk-ai` `0.16.1` and downstream AI provider packages. > > Notable: `@launchdarkly/jest` is released as **v1.0.0** (*breaking change via major version bump*), with no code changes shown here beyond the version/changelog updates. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit a09fa84. 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>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
A skeleton PR to mainly trigger the major version update for the
jesttooling moduleNote
Low Risk
Documentation-only change (link update) with no runtime or build impact.
Overview
Updates the
@launchdarkly/jestREADME to point thegetLDClient()documentation link at the newjs-coreLDClientImplAPI reference instead of the legacyjs-client-sdkdocs.Written by Cursor Bugbot for commit 535e3b4. This will update automatically on new commits. Configure here.