This repository was archived by the owner on Jun 3, 2025. It is now read-only.
Releases: launchdarkly/dotnet-sdk-common
Releases · launchdarkly/dotnet-sdk-common
Release list
7.0.0
6.2.0
[6.2.0] - 2023-10-10
Added:
- Adds locale to auto environment attribute layer.
6.1.0
[6.1.0] - 2023-10-10
Added:
- Adds ApplicationInfo and EnvironmentReporter and respective builders.
6.0.1
[6.0.1] - 2023-04-04
Fixed:
- Fixed an issue with generating the
FullyQualifiedKey. The key generation was not sorted by the kind, so the key was not stable depending on the order of the context construction. This also affected the generation of the secure mode hash for mulit-contexts.
6.0.0
[6.0.0] - 2022-12-01
This major version release of LaunchDarkly.CommonSdk corresponds to the upcoming v7.0.0 release of the LaunchDarkly server-side .NET SDK (LaunchDarkly.ServerSdk) and the v3.0.0 release of the LaunchDarkly client-side .NET SDK (LaunchDarkly.ClientSdk), and cannot be used with earlier SDK versions.
Added:
- In
LaunchDarkly.Sdk, the typesContextandContextKinddefine the new "context" model. "Contexts" are a replacement for the earlier concept of "users"; they can be populated with attributes in more or less the same way as before, but they also support new behaviors. More information about these features will be included in the release notes for theLaunchDarkly.ServerSdk7.0.0 andLaunchDarkly.ClientSdk3.0.0 releases.
Changed:
- .NET Core 2.1, .NET Framework 4.5.2, .NET Framework 4.6.1, and .NET 5.0 are now unsupported. The minimum platform versions are now .NET Core 3.1, .NET Framework 4.6.2, .NET 6.0, and .NET Standard 2.0.
- It was previously allowable to set a user key to an empty string. In the new context model, the key is not allowed to be empty. Trying to use an empty key will cause evaluations to fail and return the default value.
- There is no longer such a thing as a
Secondarymeta-attribute that affects percentage rollouts. If you set an attribute with that name in aContext, it will simply be a custom attribute like any other. - The
Anonymousattribute inLDUseris now a simple boolean, with no distinction between a false state and a null state. - There is no longer a dependency on
LaunchDarkly.JsonStream. This package existed because some platforms did not support theSystem.Text.JsonAPI, but that is no longer the case and the SDK now usesSystem.Text.Jsondirectly for all of its JSON operations. - If you are using the package
LaunchDarkly.CommonSdk.JsonNetfor interoperability with the Json.NET library, you must update this to the latest major version.
Removed:
- Removed all types, fields, and methods that were deprecated as of the most recent release.
- Removed the
Secondarymeta-attribute inUserandUserBuilder.
5.5.0
[5.5.0] - 2022-02-02
Added:
UnixMillisecondTimenow has a JSON converter like otherLaunchDarkly.Sdktypes.
Fixed:
- When using
LaunchDarkly.CommonSdk.JsonNet, nullable value types such asEvaluationReason?were not being serialized correctly.
5.4.1
[5.4.1] - 2021-11-02
Fixed:
- Copying a user with
User.Builder(existingUser)was incorrectly changing the defaultnullvalue ofAnonymousOptionaltofalse. This normally has no significance since LaunchDarkly treats those two values the same, but it could have broken tests that expected a copied user to be equal.
5.4.0
[5.4.0] - 2021-10-22
Added:
LdValue.ObjectBuilder.Remove.- User builder
Customoverloads forlonganddouble.
Changed:
- Added more doc comment text about numeric precision issues with JSON numbers.
- Updated
LaunchDarkly.JsonStreamto 1.0.3.
5.3.0
[5.3.0] - 2021-10-14
Added:
- Convenience methods for working with JSON object and array values:
LdValue.Dictionary,LdValue.List,LdValue.ObjectBuilder.Set, andLdValue.ObjectBuilder.Copy.
5.2.1
[5.2.1] - 2021-10-05
Changed:
- Changed dependency version for
System.Collections.Immutableto 1.7.1, to match the version used byLaunchDarkly.ServerSdk. This has no effect on SDK functionality, but it reduces the chance that a binding redirect will be required to reconcile dependency versions in .NET Framework.