Skip to content

chore: update lock file to pick up latest @launchdarkly/node-server-sdk 9.10.10#33

Open
kinyoklion wants to merge 1 commit intomainfrom
devin/1775466683-update-lockfile
Open

chore: update lock file to pick up latest @launchdarkly/node-server-sdk 9.10.10#33
kinyoklion wants to merge 1 commit intomainfrom
devin/1775466683-update-lockfile

Conversation

@kinyoklion
Copy link
Copy Markdown
Member

Summary

Regenerated package-lock.json to resolve the latest SDK versions within the existing >= 8.0.0 constraint in package.json. No source code changes.

Key version bumps:

Package Old New
@launchdarkly/node-server-sdk 9.2.2 9.10.10
@launchdarkly/js-sdk-common 2.3.1 2.24.0
@launchdarkly/js-server-sdk-common 2.2.2 2.18.3
launchdarkly-eventsource 2.0.1 2.2.0

The lock file was fully regenerated (rm package-lock.json && npm install), so transitive dependencies (express, body-parser, etc.) also received minor/patch bumps.

Review & Testing Checklist for Human

  • lockfileVersion changed from 2 → 3: This requires npm 7+. Verify CI and any deployment environments use a compatible npm version — if they use npm 6 or older this will break.
  • Transitive dependency https-proxy-agent jumped from ^5 to ^7 (and agent-base from 6.x to 7.x) as a side effect of the SDK update. Confirm there are no proxy-related regressions if the app runs behind a proxy.
  • Run the app locally (npm start with an SDK key) and verify the feature flag evaluation still renders correctly on the Bootstrap page.

Notes

  • The package.json version constraint (>= 8.0.0) was intentionally not changed — it already permits the latest version; only the lock file was stale.
  • The full lock file regeneration means this PR touches more than just the LD SDK lines. A narrower npm update @launchdarkly/node-server-sdk would have produced a smaller diff but may leave other stale transitive pins.

Link to Devin session: https://app.devin.ai/sessions/c8cf47d46e3f464290a65b6c05862c86
Requested by: @kinyoklion

…dk 9.10.10

Regenerated package-lock.json to resolve latest versions within the
existing '>= 8.0.0' version constraint in package.json.

- @launchdarkly/node-server-sdk: 9.2.2 -> 9.10.10
- @launchdarkly/js-sdk-common: 2.3.1 -> 2.24.0
- @launchdarkly/js-server-sdk-common: 2.2.2 -> 2.18.3
- launchdarkly-eventsource: 2.0.1 -> 2.2.0

Co-Authored-By: rlamb@launchdarkly.com <4955475+kinyoklion@users.noreply.github.com>
@devin-ai-integration
Copy link
Copy Markdown

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@devin-ai-integration
Copy link
Copy Markdown

Validation

App tested locally with updated SDK (node-server-sdk 9.10.10). Both normal and bootstrapped clients successfully evaluate flags:

hello-bootstrap running with updated SDK

@kinyoklion kinyoklion marked this pull request as ready for review April 7, 2026 16:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant