LaunchDarkly SDK versions.
The LaunchDarkly packages Versyka recognizes on npm and PyPI, their latest releases, and where the breaking changes are documented. Monitoring checks connected repositories against these every day.
Packages we track
| Package | Registry | Latest | Status | Release notes |
|---|---|---|---|---|
@launchdarkly/* | npm | each package | checked per package | — |
launchdarkly-node-server-sdklaunchdarkly-node-server-sdk was replaced by @launchdarkly/node-server-sdk. | npm | 7.0.4 | Deprecated | View → |
launchdarkly-server-sdk | PyPI | 9.18.4 | Maintained | View → |
Latest versions from the public npm and PyPI registries, checked and refreshed daily.
LaunchDarkly SDK questions
What is the latest version of the LaunchDarkly SDK?
As of 2026-10-26: launchdarkly-node-server-sdk 7.0.4 on npm; launchdarkly-server-sdk 9.18.4 on PyPI.
Versions come from the public registries and are refreshed every day.
How do I upgrade the LaunchDarkly SDK without breaking my code?
Read the release notes for every major version between yours and the latest, update each call that changed, then run your typecheck, build and tests.
- Versyka's free upgrade check shows which LaunchDarkly packages in your package.json or requirements.txt are major versions behind, with the release notes.
- Versyka can do the upgrade for you: it finds every affected LaunchDarkly call, rewrites it, runs your own tests and opens a pull request only if they pass.
Is launchdarkly-node-server-sdk deprecated?
Yes. launchdarkly-node-server-sdk is marked deprecated on npm: "This package has been replaced by @launchdarkly/node-server-sdk"
Does Versyka monitor LaunchDarkly SDKs?
Yes. Versyka recognizes @launchdarkly/* (npm), launchdarkly-node-server-sdk (npm), launchdarkly-server-sdk (PyPI) in connected repositories and flags them every day when they fall a major version behind or are deprecated.
Behind on LaunchDarkly?
Versyka finds every affected LaunchDarkly call in your code, rewrites it, runs your tests and opens a pull request.