Release 4.0.3

Security

• Bumped to 10.0.7 to address GHSA-37gx-xxp4-5rgx and GHSA-w3x6-4m5h-cxqf (both high severity).

Changed

• Upgraded 3.0.52 → 3.2.56.
• Upgraded 3.0.0 → 10.0.7.
• Upgraded 8.0.1 → 10.0.7.
• Upgraded 2.10.1 → 2.12.14.
• Upgraded 13.0.1 → 13.0.4.
• Added explicit 8.1.2 reference (previously transitive via protobuf-net 3.0.x; required to keep public API stable).
• Test deps: 8.3.0 → 9.0.1, 17.12.0 → 18.5.1, 3.0.1 → 3.1.5, 6.0.4 → 10.0.0.

v4.0.2

Fixed repository URL in NuGet package metadata.

v4.0.1

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.

[4.0.1] - 2026-01-29

Changed

• Improved NuGet package presentation: README.md is now displayed on nuget.org package page
• Enhanced package description with feature highlights
• Added more comprehensive package tags for better discoverability

[4.0.0] - 2025-01-29

Breaking Changes

• Dropped support for .NET 6.0 and .NET 7.0. The library now targets .NET 8.0 and .NET 9.0.
• StackExchange.Redis upgraded to 2.10.1. If you pass RedisChannel values directly, you must now use RedisChannel.Literal() or RedisChannel.Pattern() instead of implicit string conversion.

Changed

• Updated StackExchange.Redis from 2.0.495 to 2.10.1
• Updated System.Runtime.Caching from 4.7.0 to 8.0.1
• Added explicit reference to System.Security.Cryptography.Xml 8.0.2

Security

• Fixed Critical vulnerability in System.Drawing.Common 4.7.0 (GHSA-rxg9-xrhp-64gj)
• Fixed High vulnerability in System.IO.Pipelines 4.5.0 (GHSA-j378-6mmw-hqfr)
• Fixed Moderate vulnerability in System.Security.Cryptography.Xml 4.5.0 (GHSA-vh55-786g-wjwj)

Migration Guide

Target Framework

Update your project to target .NET 8.0 or later:

<TargetFramework>net8.0</TargetFramework>

RedisChannel API

If you're using RedisInvalidationSender or RedisInvalidationReceiver with a string channel name, update to use the explicit RedisChannel.Literal() method:

// Before (v3.x)
var sender = new RedisInvalidationSender(subscriber, "my-channel");

// After (v4.0)
var sender = new RedisInvalidationSender(subscriber, RedisChannel.Literal("my-channel"));

[3.3] and earlier

See GitHub Releases for previous versions.

v4.0.0

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.

[4.0.0] - 2025-01-29

Breaking Changes

• Dropped support for .NET 6.0 and .NET 7.0. The library now targets .NET 8.0 and .NET 9.0.
• StackExchange.Redis upgraded to 2.10.1. If you pass RedisChannel values directly, you must now use RedisChannel.Literal() or RedisChannel.Pattern() instead of implicit string conversion.

Changed

• Updated StackExchange.Redis from 2.0.495 to 2.10.1
• Updated System.Runtime.Caching from 4.7.0 to 8.0.1
• Added explicit reference to System.Security.Cryptography.Xml 8.0.2

Security

• Fixed Critical vulnerability in System.Drawing.Common 4.7.0 (GHSA-rxg9-xrhp-64gj)
• Fixed High vulnerability in System.IO.Pipelines 4.5.0 (GHSA-j378-6mmw-hqfr)
• Fixed Moderate vulnerability in System.Security.Cryptography.Xml 4.5.0 (GHSA-vh55-786g-wjwj)

Migration Guide

Target Framework

Update your project to target .NET 8.0 or later:

<TargetFramework>net8.0</TargetFramework>

RedisChannel API

If you're using RedisInvalidationSender or RedisInvalidationReceiver with a string channel name, update to use the explicit RedisChannel.Literal() method:

// Before (v3.x)
var sender = new RedisInvalidationSender(subscriber, "my-channel");

// After (v4.0)
var sender = new RedisInvalidationSender(subscriber, RedisChannel.Literal("my-channel"));

[3.3] and earlier

See GitHub Releases for previous versions.

3.3 release

Bump compatibility to latest two releases of dotnetcore

What's Changed

• Bump dotnet version by @akin-tekeoglu in #34

3.2 release

Drop support for older .net versions, keeping 5 and 6 for now;
Bump Newtonsoft.JSON to 13 because of security issue.

Release 3.0.2

Bump version because of new tooling. Same changeset as 3.0.1

Release 3.0.1

Bug: fix serialization issue #30

Release 3.0.0

Initial release, please take a look at our backlog if you want to contribute!