---
name: .NET SDK
slug: launchdarkly-net-sdk
type: github
source_url: https://github.com/launchdarkly/dotnet-core
organization: LaunchDarkly
organization_slug: launchdarkly
total_releases: 56
latest_version: LaunchDarkly.ServerSdk-v8.12.0
latest_date: 2026-04-16
last_updated: 2026-04-19
tracking_since: 2024-08-27
canonical: https://releases.sh/launchdarkly/launchdarkly-net-sdk
organization_url: https://releases.sh/launchdarkly
---

<Summary type="rolling" window-days="90" release-count="9">
The .NET SDK suite pushed toward production readiness for ahead-of-time compilation and expanded extensibility in the client SDK. CommonSdk 7.2.0 shipped AOT-safe code, unblocking deployment scenarios that require compiled native binaries. The Client SDK added plugin support and identify hooks to customize behavior at key integration points, while the Server SDK stabilized context matching logic and rolled out experimental support for the next-generation flag delivery protocol (FDv2 data system).
</Summary>

<Summary type="monthly" period="March 2026" release-count="3">
The .NET SDK expanded its extensibility surface. Client SDK shipped plugin support, allowing developers to customize SDK behavior, followed by identify hooks that enable interception of user identification. The AI SDK made defaultValue optional with a sensible disabled default, simplifying integration for feature flag evaluation.
</Summary>

<Release version="LaunchDarkly.ServerSdk-v8.12.0" date="April 16, 2026" published="2026-04-16T21:33:23.000Z" url="https://github.com/launchdarkly/dotnet-core/releases/tag/LaunchDarkly.ServerSdk-v8.12.0">
## LaunchDarkly.ServerSdk: v8.12.0

## [8.12.0](https://github.com/launchdarkly/dotnet-core/compare/LaunchDarkly.ServerSdk-v8.11.2...LaunchDarkly.ServerSdk-v8.12.0) (2026-04-16)


### Features

* Make Status ToString() methods format consistent  ([#247](https://github.com/launchdarkly/dotnet-core/issues/247)) ([6373f98](https://github.com/launchdarkly/dotnet-core/commit/6373f987f27f479aa256e94ab472037623e1febc))

---
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 -->
</Release>

<Release version="LaunchDarkly.ClientSdk-v5.7.1" date="April 10, 2026" published="2026-04-10T13:11:44.000Z" url="https://github.com/launchdarkly/dotnet-core/releases/tag/LaunchDarkly.ClientSdk-v5.7.1">
## LaunchDarkly.ClientSdk: v5.7.1

## [5.7.1](https://github.com/launchdarkly/dotnet-core/compare/LaunchDarkly.ClientSdk-v5.7.0...LaunchDarkly.ClientSdk-v5.7.1) (2026-04-09)


### Bug Fixes

* Update CommonSdk to 7.2.0 and InternalSdk to 3.6.1 ([#243](https://github.com/launchdarkly/dotnet-core/issues/243)) ([9e8e5ff](https://github.com/launchdarkly/dotnet-core/commit/9e8e5ff1734548462a681ab66147acc2bd2f2895))

---
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 -->
</Release>

<Release version="LaunchDarkly.ServerSdk-v8.11.2" date="April 9, 2026" published="2026-04-09T22:33:46.000Z" url="https://github.com/launchdarkly/dotnet-core/releases/tag/LaunchDarkly.ServerSdk-v8.11.2">
## LaunchDarkly.ServerSdk: v8.11.2

## [8.11.2](https://github.com/launchdarkly/dotnet-core/compare/LaunchDarkly.ServerSdk-v8.11.1...LaunchDarkly.ServerSdk-v8.11.2) (2026-04-09)


### Bug Fixes

* Update CommonSdk to 7.2.0 and InternalSdk to 3.6.1 ([#243](https://github.com/launchdarkly/dotnet-core/issues/243)) ([9e8e5ff](https://github.com/launchdarkly/dotnet-core/commit/9e8e5ff1734548462a681ab66147acc2bd2f2895))

---
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 -->
</Release>

<Release version="LaunchDarkly.CommonSdk-v7.2.0" date="April 8, 2026" published="2026-04-08T22:00:25.000Z" url="https://github.com/launchdarkly/dotnet-core/releases/tag/LaunchDarkly.CommonSdk-v7.2.0">
## LaunchDarkly.CommonSdk: v7.2.0

## [7.2.0](https://github.com/launchdarkly/dotnet-core/compare/LaunchDarkly.CommonSdk-v7.1.1...LaunchDarkly.CommonSdk-v7.2.0) (2026-04-08)


### Features

* Make common sdk AOT safe ([#169](https://github.com/launchdarkly/dotnet-core/issues/169)) ([8c6948e](https://github.com/launchdarkly/dotnet-core/commit/8c6948ea89d3c71abc24e6e0284a5dde62bd54b3))

---
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 -->
</Release>

<Release version="LaunchDarkly.ClientSdk-v5.7.0" date="March 13, 2026" published="2026-03-13T21:34:10.000Z" url="https://github.com/launchdarkly/dotnet-core/releases/tag/LaunchDarkly.ClientSdk-v5.7.0">
## LaunchDarkly.ClientSdk: v5.7.0

## [5.7.0](https://github.com/launchdarkly/dotnet-core/compare/LaunchDarkly.ClientSdk-v5.6.0...LaunchDarkly.ClientSdk-v5.7.0) (2026-03-13)


### Features

* Add Identify hooks to Client SDK ([#234](https://github.com/launchdarkly/dotnet-core/issues/234)) ([ddbb81f](https://github.com/launchdarkly/dotnet-core/commit/ddbb81fd3be7bf7b6c49962c5fa4b2a93b9cf44c))

---
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 -->
</Release>

<Release version="LaunchDarkly.ServerSdk.Ai-v0.9.3" date="March 5, 2026" published="2026-03-05T15:19:32.000Z" url="https://github.com/launchdarkly/dotnet-core/releases/tag/LaunchDarkly.ServerSdk.Ai-v0.9.3">
## LaunchDarkly.ServerSdk.Ai: v0.9.3

## [0.9.3](https://github.com/launchdarkly/dotnet-core/compare/LaunchDarkly.ServerSdk.Ai-v0.9.2...LaunchDarkly.ServerSdk.Ai-v0.9.3) (2026-03-05)


### Bug Fixes

* Make defaultValue optional with a disabled default ([#232](https://github.com/launchdarkly/dotnet-core/issues/232)) ([f69d420](https://github.com/launchdarkly/dotnet-core/commit/f69d42034bb960f83b831d2edf6788f70a20ceed))

---
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 -->
</Release>

<Release version="LaunchDarkly.ClientSdk-v5.6.0" date="March 3, 2026" published="2026-03-03T19:34:12.000Z" url="https://github.com/launchdarkly/dotnet-core/releases/tag/LaunchDarkly.ClientSdk-v5.6.0">
## LaunchDarkly.ClientSdk: v5.6.0

## [5.6.0](https://github.com/launchdarkly/dotnet-core/compare/LaunchDarkly.ClientSdk-v5.5.4...LaunchDarkly.ClientSdk-v5.6.0) (2026-03-03)


### Features

* Add plugin support to Client SDK ([#229](https://github.com/launchdarkly/dotnet-core/issues/229)) ([ce5cdd9](https://github.com/launchdarkly/dotnet-core/commit/ce5cdd989ef3850e80a61125b4cc3c36ae23b1a9))

---
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 -->
</Release>

<Release version="LaunchDarkly.ServerSdk.Ai-v0.9.2" date="February 25, 2026" published="2026-02-25T23:14:37.000Z" url="https://github.com/launchdarkly/dotnet-core/releases/tag/LaunchDarkly.ServerSdk.Ai-v0.9.2">
## LaunchDarkly.ServerSdk.Ai: v0.9.2

## [0.9.2](https://github.com/launchdarkly/dotnet-core/compare/LaunchDarkly.ServerSdk.Ai-v0.9.1...LaunchDarkly.ServerSdk.Ai-v0.9.2) (2026-02-25)


### Bug Fixes

* Improve usage reporting ([#228](https://github.com/launchdarkly/dotnet-core/issues/228)) ([376b6b0](https://github.com/launchdarkly/dotnet-core/commit/376b6b0cbca28c7b49e5f64ee54b1f6d317d99fa))

---
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 -->
</Release>

<Release version="LaunchDarkly.ServerSdk-v8.11.1" date="February 17, 2026" published="2026-02-17T23:22:11.000Z" url="https://github.com/launchdarkly/dotnet-core/releases/tag/LaunchDarkly.ServerSdk-v8.11.1">
## LaunchDarkly.ServerSdk: v8.11.1

## [8.11.1](https://github.com/launchdarkly/dotnet-core/compare/LaunchDarkly.ServerSdk-v8.11.0...LaunchDarkly.ServerSdk-v8.11.1) (2026-02-17)


### Bug Fixes

* IfMatchContext/AndMatchContext utilize context kind. ([#225](https://github.com/launchdarkly/dotnet-core/issues/225)) ([95bc949](https://github.com/launchdarkly/dotnet-core/commit/95bc9495984976833efd736f36fc4023c37eb663))

---
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 -->
</Release>

<Release version="LaunchDarkly.ServerSdk-v8.11.0" date="January 12, 2026" published="2026-01-12T20:40:55.000Z" url="https://github.com/launchdarkly/dotnet-core/releases/tag/LaunchDarkly.ServerSdk-v8.11.0">
## LaunchDarkly.ServerSdk: v8.11.0

## [8.11.0](https://github.com/launchdarkly/dotnet-core/compare/LaunchDarkly.ServerSdk-v8.10.4...LaunchDarkly.ServerSdk-v8.11.0) (2026-01-12)


### Features

* **experimental:** Release EAP support for FDv2 data system. ([d78799a](https://github.com/launchdarkly/dotnet-core/commit/d78799acb38323c8ca7207046b41570e1d333a28))


### Bug Fixes

* Update FileDataSource to process reload triggers under lock. ([#199](https://github.com/launchdarkly/dotnet-core/issues/199)) ([75f51c6](https://github.com/launchdarkly/dotnet-core/commit/75f51c67bff8ccf36035a948763998c10f083dbd))

### Data Saving Mode EAP

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.

## Configuration

There are a number of pre-defined configurations available for the data system depending on the SDK deployment.

### Default

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.



```csharp
var config = Configuration.Builder("your-sdk-key")
    .DataSystem(Components.DataSystem().Default())
    .Build();
```

### Polling Only or Streaming Only

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:
```csharp
var config = Configuration.Builder(Environment.GetEnvironmentVariable("LAUNCHDARKLY_SDK_KEY"))
    .DataSystem(Components.DataSystem().Polling())
    .Build();
```

Streaming:
```csharp
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.

### With a Persistent Store

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:
```csharp
var config = Configuration.Builder(Environment.GetEnvironmentVariable("LAUNCHDARKLY_SDK_KEY"))
    .DataSystem(Components.DataSystem().PersistentStore(Components.PersistentDataStore(Redis.DataStore())))
    .Build();
```

### Daemon Mode

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:
```csharp
var config = Configuration.Builder(Environment.GetEnvironmentVariable("LAUNCHDARKLY_SDK_KEY"))
    .DataSystem(Components.DataSystem().Daemon(Components.PersistentDataStore(Redis.DataStore())))
    .Build();
```

### Offline

The top-level `Offline` configuration applies to the data system.

```csharp
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.

```csharp
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](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).

<!-- CURSOR_SUMMARY -->
</Release>

<Release version="LaunchDarkly-ServerSdk-8.11.0-beta.1" date="December 19, 2025" published="2025-12-19T21:44:42.000Z" url="https://github.com/launchdarkly/dotnet-core/releases/tag/LaunchDarkly-ServerSdk-8.11.0-beta.1">
## LaunchDarkly-ServerSdk-8.11.0-beta.1 

This release contains support for our second generation flag delivery protocol, also known as data-saving mode.

It is available via nuget: https://www.nuget.org/packages/LaunchDarkly.ServerSdk/8.11.0-beta.1

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.

## Configuration

There are a number of pre-defined configurations available for the data system depending on the SDK deployment.

### Default

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.



```csharp
var config = Configuration.Builder("your-sdk-key")
    .DataSystem(Components.DataSystem().Default())
    .Build();
```

### Polling Only or Streaming Only

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:
```csharp
var config = Configuration.Builder(Environment.GetEnvironmentVariable("LAUNCHDARKLY_SDK_KEY"))
    .DataSystem(Components.DataSystem().Polling())
    .Build();
```

Streaming:
```csharp
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.

### With a Persistent Store

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:
```csharp
var config = Configuration.Builder(Environment.GetEnvironmentVariable("LAUNCHDARKLY_SDK_KEY"))
    .DataSystem(Components.DataSystem().PersistentStore(Components.PersistentDataStore(Redis.DataStore())))
    .Build();
```

### Daemon Mode

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:
```csharp
var config = Configuration.Builder(Environment.GetEnvironmentVariable("LAUNCHDARKLY_SDK_KEY"))
    .DataSystem(Components.DataSystem().Daemon(Components.PersistentDataStore(Redis.DataStore())))
    .Build();
```

### Offline

The top-level `Offline` configuration applies to the data system.

```csharp
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.

```csharp
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.

## Known Issues

- When a persistent store experiences an outage while the SDK is attempting to write to it, then when that store later recovers it may not be updated to the current state. The in-memory state of the SDK will still contain all updates it has received.

- `Components.ExternalUpdatesOnly` should not be used as a `DataSystem` initializer or synchronizer. This component doesn't emit any payloads, and will result in an initialization timeout.

</Release>

<Release version="LaunchDarkly.ServerSdk-v8.10.4" date="November 10, 2025" published="2025-11-10T21:02:18.000Z" url="https://github.com/launchdarkly/dotnet-core/releases/tag/LaunchDarkly.ServerSdk-v8.10.4">
## LaunchDarkly.ServerSdk: v8.10.4

## [8.10.4](https://github.com/launchdarkly/dotnet-core/compare/LaunchDarkly.ServerSdk-v8.10.3...LaunchDarkly.ServerSdk-v8.10.4) (2025-11-10)


### Bug Fixes

* Use thread-safe hash for big segments hashing. ([#180](https://github.com/launchdarkly/dotnet-core/issues/180)) ([06196d8](https://github.com/launchdarkly/dotnet-core/commit/06196d881d306e2bd09631469c657a4f11685fcc))

---
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 -->
</Release>

<Release version="LaunchDarkly.ServerSdk.DynamoDB-v5.0.0" date="October 22, 2025" published="2025-10-22T14:09:17.000Z" url="https://github.com/launchdarkly/dotnet-core/releases/tag/LaunchDarkly.ServerSdk.DynamoDB-v5.0.0">
## LaunchDarkly.ServerSdk.DynamoDB: v5.0.0

## [5.0.0](https://github.com/launchdarkly/dotnet-core/compare/LaunchDarkly.ServerSdk.DynamoDB-v4.0.2...LaunchDarkly.ServerSdk.DynamoDB-v5.0.0) (2025-10-22)


### ⚠ BREAKING CHANGES

* Drop support for AWSSDK.DynamoDB v3 ([#173](https://github.com/launchdarkly/dotnet-core/issues/173))

### Features

* Support AWSSDK.DynamoDB v4 ([#173](https://github.com/launchdarkly/dotnet-core/issues/173)) ([05c16c1](https://github.com/launchdarkly/dotnet-core/commit/05c16c16865f6978df2cd6eb9b057bdbbacb4aad))

---
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 -->
</Release>

<Release version="LaunchDarkly.ServerSdk.DynamoDB-v4.0.2" date="October 22, 2025" published="2025-10-22T00:06:23.000Z" url="https://github.com/launchdarkly/dotnet-core/releases/tag/LaunchDarkly.ServerSdk.DynamoDB-v4.0.2">
## LaunchDarkly.ServerSdk.DynamoDB: v4.0.2

## [4.0.2](https://github.com/launchdarkly/dotnet-core/compare/LaunchDarkly.ServerSdk.DynamoDB-v4.0.1...LaunchDarkly.ServerSdk.DynamoDB-v4.0.2) (2025-10-21)


### Bug Fixes

* Fix package deployment process ([#174](https://github.com/launchdarkly/dotnet-core/issues/174)) ([3b2ce8b](https://github.com/launchdarkly/dotnet-core/commit/3b2ce8b88610f12b94d79c815eeba6a49f9cbeed))
* Prevent using incompatible AWS version ([#171](https://github.com/launchdarkly/dotnet-core/issues/171)) ([5496a64](https://github.com/launchdarkly/dotnet-core/commit/5496a64bedc2bc25fdf8ca9757345de25b67f38f))

---
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 -->
</Release>

<Release version="LaunchDarkly.ServerSdk.DynamoDb-v4.0.1" date="October 21, 2025" published="2025-10-21T20:35:38.000Z" url="https://github.com/launchdarkly/dotnet-core/releases/tag/LaunchDarkly.ServerSdk.DynamoDb-v4.0.1">
## LaunchDarkly.ServerSdk.DynamoDb: v4.0.1

## [4.0.1](https://github.com/launchdarkly/dotnet-core/compare/LaunchDarkly.ServerSdk.DynamoDb-v4.0.0...LaunchDarkly.ServerSdk.DynamoDb-v4.0.1) (2025-10-21)


### Bug Fixes

* Prevent using incompatible AWS version ([#171](https://github.com/launchdarkly/dotnet-core/issues/171)) ([5496a64](https://github.com/launchdarkly/dotnet-core/commit/5496a64bedc2bc25fdf8ca9757345de25b67f38f))

---
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 -->
</Release>

<Release version="LaunchDarkly.ServerSdk.Telemetry-v1.4.0" date="October 7, 2025" published="2025-10-07T15:47:28.000Z" url="https://github.com/launchdarkly/dotnet-core/releases/tag/LaunchDarkly.ServerSdk.Telemetry-v1.4.0">
## LaunchDarkly.ServerSdk.Telemetry: v1.4.0

## [1.4.0](https://github.com/launchdarkly/dotnet-core/compare/LaunchDarkly.ServerSdk.Telemetry-v1.3.0...LaunchDarkly.ServerSdk.Telemetry-v1.4.0) (2025-10-06)


### Features

* add all available attributes to a span ([#167](https://github.com/launchdarkly/dotnet-core/issues/167)) ([7350aac](https://github.com/launchdarkly/dotnet-core/commit/7350aac8ef35630b0273d3b12d34e77fa682ff9c))

---
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 -->
</Release>

<Release version="LaunchDarkly.ClientSdk-v5.5.4" date="September 29, 2025" published="2025-09-29T16:28:26.000Z" url="https://github.com/launchdarkly/dotnet-core/releases/tag/LaunchDarkly.ClientSdk-v5.5.4">
## LaunchDarkly.ClientSdk: v5.5.4

## [5.5.4](https://github.com/launchdarkly/dotnet-core/compare/LaunchDarkly.ClientSdk-v5.5.3...LaunchDarkly.ClientSdk-v5.5.4) (2025-09-29)


### Bug Fixes

* Validate string format of SDK key ([#162](https://github.com/launchdarkly/dotnet-core/issues/162)) ([27a26fb](https://github.com/launchdarkly/dotnet-core/commit/27a26fb9e226f7e5208928d9df43fbd6d5a68037))

---
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 -->
</Release>

<Release version="LaunchDarkly.ServerSdk-v8.10.3" date="September 29, 2025" published="2025-09-29T15:50:42.000Z" url="https://github.com/launchdarkly/dotnet-core/releases/tag/LaunchDarkly.ServerSdk-v8.10.3">
## LaunchDarkly.ServerSdk: v8.10.3

## [8.10.3](https://github.com/launchdarkly/dotnet-core/compare/LaunchDarkly.ServerSdk-v8.10.2...LaunchDarkly.ServerSdk-v8.10.3) (2025-09-29)


### Bug Fixes

* Validate string format of SDK key ([#162](https://github.com/launchdarkly/dotnet-core/issues/162)) ([27a26fb](https://github.com/launchdarkly/dotnet-core/commit/27a26fb9e226f7e5208928d9df43fbd6d5a68037))
</Release>

<Release version="LaunchDarkly.CommonSdk-v7.1.1" date="September 26, 2025" published="2025-09-26T22:05:04.000Z" url="https://github.com/launchdarkly/dotnet-core/releases/tag/LaunchDarkly.CommonSdk-v7.1.1">
## LaunchDarkly.CommonSdk: v7.1.1

## [7.1.1](https://github.com/launchdarkly/dotnet-core/compare/LaunchDarkly.CommonSdk-v7.1.0...LaunchDarkly.CommonSdk-v7.1.1) (2025-09-26)


### Bug Fixes

* Add validation format check for SDK key ([#163](https://github.com/launchdarkly/dotnet-core/issues/163)) ([02c6ed7](https://github.com/launchdarkly/dotnet-core/commit/02c6ed793f1984cce878f0c53667476533acb896))
</Release>

<Release version="LaunchDarkly.ClientSdk-v5.5.3" date="September 25, 2025" published="2025-09-25T17:44:38.000Z" url="https://github.com/launchdarkly/dotnet-core/releases/tag/LaunchDarkly.ClientSdk-v5.5.3">
## LaunchDarkly.ClientSdk: v5.5.3

## [5.5.3](https://github.com/launchdarkly/dotnet-core/compare/LaunchDarkly.ClientSdk-v5.5.2...LaunchDarkly.ClientSdk-v5.5.3) (2025-09-25)


### Bug Fixes

* Update EventSource to 5.2.1 ([#159](https://github.com/launchdarkly/dotnet-core/issues/159)) ([35d08d7](https://github.com/launchdarkly/dotnet-core/commit/35d08d7160512850c6d3a81e4fc312696cbb808e))
</Release>

<Pagination page="1" total-pages="3" total-items="56" next="https://releases.sh/launchdarkly/launchdarkly-net-sdk.md?page=2" />