NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
NuGet
NuGet, #647 most downloaded on NuGet
LaunchDarkly Server-Side .NET SDK
Latest stable
8.17.2
Last release 1 months ago
05 Oct 2026
Ships fairly regularly
a new release about every 5 weeks
Some releases are documented
notes for 29 of the last 60 stable releases
14 versions withdrawn
withdrawn after publishing
127 years old
78 releases · first in 1900
Drag across the ruler to compare, or tap a release to open it.
Bump LaunchDarkly.InternalSdk to 3.11.1 for redactedAttributes escaping
This PR was generated with Release Please. See documentation.
update LaunchDarkly.Logging to 2.1.0 in server SDK
Your coding agent can read these notes before it upgrades. Set up the MCP server →
SDK no longer shuts down data sources when SDK keys are invalid. Conform FDv1 streaming and polling data sources to the RETRY spec
SDK no longer shuts down data sources when SDK keys are invalid. HTTP responses that previously caused a data source to permanently stop — 401, 403, and other 4xx — no longer terminate it. Streaming enters an extended backoff regime starting at 5 minutes and doubling to a 1 hour ceiling; polling continues at its configured interval but engages the extended regime after an unexpected failure. Streaming returns to normal backoff after 60 seconds of continuous healthy operation; polling returns to its normal cadence after two consecutive successful polls.
Consequences visible to applications:
DataSourceState.Off no longer indicates a rejected SDK key. Off is now reached only by explicit shutdown. Inspect DataSourceStatusProvider.Status.LastError instead, which reports ErrorKind.ErrorResponse with the HTTP status code while the data source keeps retrying.
The LdClient constructor waits out StartWaitTime when the SDK key is rejected. Because an invalid key no longer ends initialization, the constructor blocks for the full StartWaitTime (default 10 seconds) rather than returning as soon as the 401 arrives.
FDv2 falls back to FDv1 on a rejected key more slowly. The FDv1 synchronizer is no longer blacklisted on an unrecoverable error, so fallback now occurs via the 2 minute interrupted timeout instead of immediately.
Polling interval is measured from completion rather than from start. The effective period is now the configured interval plus the duration of each poll.
This PR was generated with Release Please. See documentation.
Log the cached-data evaluation warning only once per client
polling 304 responses handled appropriately
bump LaunchDarkly.InternalSdk pins to 3.10.1
This PR was generated with Release Please. See documentation.
Support server-side gzip for polling
update LaunchDarkly.EventSource to 5.3.1 for Authenticode-signed assemblies
Drop persistent-store cache after FDv2 in-memory store init
This PR was generated with Release Please. See documentation.
<!-- CURSOR_SUMMARY -->
add X-LaunchDarkly-Instance-Id header
This PR was generated with Release Please. See documentation.
<!-- CURSOR_SUMMARY -->
exclude documentation files from NuGet package builds
This PR was generated with Release Please. See documentation.
<!-- CURSOR_SUMMARY -->
Honor x-ld-fd-fallback header in FDv2 initializer phase and on successful responses
This PR was generated with Release Please. See documentation.
<!-- CURSOR_SUMMARY -->
Make Status ToString() methods format consistent
This PR was generated with Release Please. See documentation.
<!-- CURSOR_SUMMARY -->
Update CommonSdk to 7.2.0 and InternalSdk to 3.6.1
This PR was generated with Release Please. See documentation.
<!-- CURSOR_SUMMARY -->
IfMatchContext/AndMatchContext utilize context kind.
This PR was generated with Release Please. See documentation.
<!-- CURSOR_SUMMARY -->
experimental: Release EAP support for FDv2 data system.
This release contains support for our second generation flag delivery protocol, also known as data-saving mode.
This SDK version will operate using our first generation flag delivery protocol unless configured specifcally to use our new protocol.
In the SDK support for the new protocol is defined by a DataSystem. Configuring a DataSystem will enable the use of the new protocol.
The DataSystem includes a more sophisticated configuration for initializers, which are a means of getting an initial SDK payload, and synchronizers which keep the SDK up to date.
There are a number of pre-defined configurations available for the data system depending on the SDK deployment.
This is the LaunchDarkly recommended default setting for the data system. This configuration uses a two-phase strategy for initialization (getting you) as well as including fallbacks for synchronization.
The SDK will attempt to get an initial payload by making a single poll to our polling endpoints, and then will keep that payload up to date via streaming. If that initial polling process fails, then the SDK can still initialize via streaming once it enters its synchronization phase. Similarly, in the synchronization phase, the SDK can fallback to polling if it experiences issues with streaming.
var config = Configuration.Builder("your-sdk-key")
.DataSystem(Components.DataSystem().Default())
.Build();
The SDK can be configured to only use polling, or only use streaming. This isn't the recommended mode, and in this mode there are not as many fallbacks available.
Polling:
var config = Configuration.Builder(Environment.GetEnvironmentVariable("LAUNCHDARKLY_SDK_KEY"))
.DataSystem(Components.DataSystem().Polling())
.Build();
Streaming:
var config = Configuration.Builder(Environment.GetEnvironmentVariable("LAUNCHDARKLY_SDK_KEY"))
.DataSystem(Components.DataSystem().Streaming())
.Build();
Note that in streaming only mode polling may still be used if we need to disable our second generation protocol. In this case the data system will receive a request to fallback to our v1 protocol and it will use polling to do so.
When configured with a persistent store the SDK uses the same strategy for initialization and synchronization as Default, but with the addition of a persistent store.
If flags are evaluated before the SDK has finished initializing, then cached values can be used from the store. Once the SDK initialization process completes flags are kept up to date in a memory cache, and persisted into the store. Flags are always maintained in memory after initialization, versus our previous implementation which used a TTL on each item.
When using a persistent store you will need to use our persistence integrations.
Using a redis persistent store:
var config = Configuration.Builder(Environment.GetEnvironmentVariable("LAUNCHDARKLY_SDK_KEY"))
.DataSystem(Components.DataSystem().PersistentStore(Components.PersistentDataStore(Redis.DataStore())))
.Build();
When using daemon mode the SDK doesn't request a flag payload from LaunchDarkly. Instead it depends on flags being written to a persistent store instance by the relay proxy.
In this mode configuration is read from a store as needed and cached in memory with a TTL. The TTL determines how fresh the data for any given item will be.
Using a redis persistent store:
var config = Configuration.Builder(Environment.GetEnvironmentVariable("LAUNCHDARKLY_SDK_KEY"))
.DataSystem(Components.DataSystem().Daemon(Components.PersistentDataStore(Redis.DataStore())))
.Build();
The top-level Offline configuration applies to the data system.
var config = Configuration.Builder(Environment.GetEnvironmentVariable("LAUNCHDARKLY_SDK_KEY"))
.Offline(true)
.Build();
If the Offline(true) and a DataSystem(...) are both specified, then the initializers and synchronizers of the data system configuration will not be used.
var config = Configuration.Builder(Environment.GetEnvironmentVariable("LAUNCHDARKLY_SDK_KEY"))
.Offline(true)
.DataSystem(Components.DataSystem().Default())
.Build();
The DataSystem does not require the use of Components.ExternalUpdatesOnly. With the DataSystem the equivalent is to not specify any initializers, synchronizers, or fallback synchronizer.
This PR was generated with Release Please. See documentation.
<!-- CURSOR_SUMMARY -->
Use thread-safe hash for big segments hashing.
This PR was generated with Release Please. See documentation.
<!-- CURSOR_SUMMARY -->
Validate string format of SDK key
## 8.10.2 (2025-09-25) ### Bug Fixes * Update EventSource to 5.2.1
## 8.10.1 (2025-08-26) ### Bug Fixes * Bump Internal SDK to 3.5.4
Add experimental plugin support
Invalid circular reference detection for nested segments
Track latencies greater than 1 second
## 8.9.0 (2025-06-02) ### Features * Update to net8 (ddae814) ### Bug Fixes * #104 dependency optimisation (#111) (2c7ff62) * Bump Internal SDK versio
Inline context for custom and migrations op events
Add environment ID support for hooks.
report prerequisite relations in AllFlagState
improved accuracy of stream interruption error message.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
bump LaunchDarkly.InternalSdk pins to 3.10.1
This PR was generated with Release Please. See documentation.
One column per quarter.