Upgrading StackExchange.Redis 2 to 3
Breaking2.13.17 → 3.4.29Breaking3Security1Platform1Deprecated1New26Changed25Fixed43Other43
Fetching 26 releases from GitHub…25 / 26
BreakingUpgrade verdict
3 breaking changes and a platform requirement change and a security fix.
In plain terms
- Code that still uses features the library said it would remove now fails with an error instead of a warning, so it must be updated before upgrading.
- If you relied on the host name in your configuration being used for TLS even when the cluster advertised a different name, that no longer happens unless you set SslHost explicitly.
- Commands that require admin permission now fail immediately on the client unless admin access is turned on, instead of being sent to the server.
- The package no longer includes a .NET 6 specific build.
Must act Top 5 of 6 that need code or config changes
Target frameworks requirement changed in 3.2.0: .NETFramework4.6.1, .NETFramework4.7.2, .NETStandard2.0, net10.0, net6.0, net8.0 → .NETFramework4.6.1, .NETFramework4.7.2, .NETStandard2.0, net10.0, net8.0.
What you must change
Breaking3
Turns the previously warned "we will remove this in 3.0" features into errors and reframes the removal target as 3.2.
Advertised host names now take precedence over the declared configuration host name when SslHost is not specified.
SslHostExecute[Async] now detects admin commands protected by AllowAdmin and throws client-side when AllowAdmin is not enabled.
ExecuteExecuteAsyncAllowAdminSecurity1
Bumps SourceLink past CVE-2026-62900, and System.IO.Hashing with it.
SourceLinkSystem.IO.HashingPlatform1
Drops net6.0 from TargetFrameworks.
net6.0Deprecations to plan for
Deprecated1
Obsolete messages now point at 4.0, since 3.2 shipped without them.