Releases: intelligenthack/intelligentcache
v4.0.2
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
RedisChannelvalues directly, you must now useRedisChannel.Literal()orRedisChannel.Pattern()instead of implicit string conversion.
Changed
- Updated
StackExchange.Redisfrom 2.0.495 to 2.10.1 - Updated
System.Runtime.Cachingfrom 4.7.0 to 8.0.1 - Added explicit reference to
System.Security.Cryptography.Xml8.0.2
Security
- Fixed Critical vulnerability in
System.Drawing.Common4.7.0 (GHSA-rxg9-xrhp-64gj) - Fixed High vulnerability in
System.IO.Pipelines4.5.0 (GHSA-j378-6mmw-hqfr) - Fixed Moderate vulnerability in
System.Security.Cryptography.Xml4.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
RedisChannelvalues directly, you must now useRedisChannel.Literal()orRedisChannel.Pattern()instead of implicit string conversion.
Changed
- Updated
StackExchange.Redisfrom 2.0.495 to 2.10.1 - Updated
System.Runtime.Cachingfrom 4.7.0 to 8.0.1 - Added explicit reference to
System.Security.Cryptography.Xml8.0.2
Security
- Fixed Critical vulnerability in
System.Drawing.Common4.7.0 (GHSA-rxg9-xrhp-64gj) - Fixed High vulnerability in
System.IO.Pipelines4.5.0 (GHSA-j378-6mmw-hqfr) - Fixed Moderate vulnerability in
System.Security.Cryptography.Xml4.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!
