Releasing version 3.0.2

launchdarkly · Apr 4, 2023 · d1ecf7a · d1ecf7a
1 parent e865f7c
commit d1ecf7a
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 1 deletion.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -3,6 +3,12 @@
 All notable changes to the LaunchDarkly Client-Side SDK for .NET will be documented in this file.
 This project adheres to [Semantic Versioning](http://semver.org).
 
+## [3.0.2] - 2023-04-04
+When using multi-contexts, then this update can change the `FullyQualifiedKey` for a given context. This can cause a cache miss in the local cache for a given context, requiring a connection to LaunchDarkly to populate that cache for the new `FullyQualifiedKey`.
+
+### 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 affects how flags are locally cached, as they are cached by the FullyQualifiedKey.
+
 ## [3.0.1] - 2023-03-08
 ### Changed:
 - Update to `LaunchDarkly.InternalSdk` `3.1.1`

diff --git a/src/LaunchDarkly.ClientSdk/LaunchDarkly.ClientSdk.csproj b/src/LaunchDarkly.ClientSdk/LaunchDarkly.ClientSdk.csproj
@@ -1,7 +1,7 @@
 <Project Sdk="MSBuild.Sdk.Extras">
 
   <PropertyGroup>
-    <Version>3.0.1</Version>
+    <Version>3.0.2</Version>
     <!-- The BUILDFRAMEWORKS variable allows us to override the target frameworks in
          a situation where we need to build only the .NET Standard target and do not
          want to even mention the Android/iOS targets, because we're in an environment