From b45146ba71e45575219bc2879011be96f09dcd8d Mon Sep 17 00:00:00 2001 From: Graham Watts Date: Thu, 18 Jul 2024 08:06:04 +0300 Subject: [PATCH] Mitigation for CVE-2024-30105/GHSA-hh2w-p6rv-4g7w (#406) Mitigates https://github.com/advisories/GHSA-hh2w-p6rv-4g7w --- Directory.Packages.props | 2 +- docs/release-notes/v5.0.0.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Directory.Packages.props b/Directory.Packages.props index 53322108..ef6c60f9 100644 --- a/Directory.Packages.props +++ b/Directory.Packages.props @@ -59,7 +59,7 @@ - + diff --git a/docs/release-notes/v5.0.0.md b/docs/release-notes/v5.0.0.md index 10144d15..053978ee 100644 --- a/docs/release-notes/v5.0.0.md +++ b/docs/release-notes/v5.0.0.md @@ -29,7 +29,7 @@ This release includes the following changes and features: ## String Caching -The new `StringCache` class is now used to cache feequently-used string instances instead of using `string.Intern` directly. `StringCache` uses a `ConcurrentDictionary` to cache string instances; benchmarks show that this usually gives superior performance compared to `string.Intern`. `StringCache` can be configured to use `string.Intern` instead of its own cache by setting the `DataCore.Adapter.StringCache.UseNativeIntern` flag on `AppContext` to `false`. +The new `StringCache` class is now used to cache frequently-used string instances instead of using `string.Intern` directly. `StringCache` uses a `ConcurrentDictionary` to cache string instances; benchmarks show that this usually gives superior performance compared to `string.Intern`. `StringCache` can be configured to use `string.Intern` instead of its own cache by setting the `DataCore.Adapter.StringCache.UseNativeIntern` flag on `AppContext` to `false`. Additionally, new `string` extension methods have been added in the `System` namespace to allow strings to be interned easily using `StringCache`: