Update dependency StackExchange.Redis to v3 - #319
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/stackexchange.redis-3.x
branch
2 times, most recently
from
June 29, 2026 04:14
1d1d859 to
fd5b83e
Compare
renovate
Bot
force-pushed
the
renovate/stackexchange.redis-3.x
branch
2 times, most recently
from
July 13, 2026 11:32
e1e9c30 to
b6f7725
Compare
renovate
Bot
force-pushed
the
renovate/stackexchange.redis-3.x
branch
3 times, most recently
from
August 3, 2026 17:07
88002a6 to
c0e1df3
Compare
renovate
Bot
force-pushed
the
renovate/stackexchange.redis-3.x
branch
from
August 6, 2026 15:02
c0e1df3 to
c9aba60
Compare
renovate
Bot
force-pushed
the
renovate/stackexchange.redis-3.x
branch
from
August 21, 2026 16:53
c9aba60 to
b18dec4
Compare
renovate
Bot
force-pushed
the
renovate/stackexchange.redis-3.x
branch
2 times, most recently
from
August 31, 2026 01:35
b18dec4 to
a97c53f
Compare
renovate
Bot
force-pushed
the
renovate/stackexchange.redis-3.x
branch
from
September 10, 2026 22:58
a97c53f to
9f08060
Compare
renovate
Bot
force-pushed
the
renovate/stackexchange.redis-3.x
branch
from
September 13, 2026 17:07
9f08060 to
1ade891
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.13.1→3.2.1Release Notes
StackExchange/StackExchange.Redis (StackExchange.Redis)
v3.2.1Compare Source
What's Changed
Full Changelog: StackExchange/StackExchange.Redis@3.2.0...3.2.1
v3.2.0Compare Source
Highlights
BITFIELDsupportEVAL_RO/EVALSHA_ROsupport (gated by server-version)ExecuteRespandScriptEvaluateRespAPIs for performing ad-hoc commands much more efficientlyCLUSTER NODEStoCLUSTER SLOTS, improving life-cycle and identityWhat's Changed
Background work
New Contributors
Full Changelog: StackExchange/StackExchange.Redis@3.1.31...3.2.0
v3.1.31Compare Source
What's Changed
Features
Internal bits
Auxiliary bits
New Contributors
Full Changelog: StackExchange/StackExchange.Redis@3.1.13...3.1.31
v3.1.13Compare Source
What's Changed
New Contributors
Full Changelog: StackExchange/StackExchange.Redis@3.1.11...3.1.13
v3.1.11Compare Source
What's Changed
KeyTypehandling of "none" by @mgravell in #3160!@nameis a Linux abstract Unix socket by @mgravell in #3165WithRetry: implement fine-grained (arg-specific) command retry categories by @mgravell in #3161Internal pieces
Full Changelog: StackExchange/StackExchange.Redis@3.1.3...3.1.11
v3.1.3Compare Source
This release should be considered a minor tweak to the much more significant 3.1.0 - please see the release notes for 3.1.0.
What's Changed
WithRetry().CreateTransaction(...)should: ITransactionby @mgravell in #3151New Contributors
Full Changelog: StackExchange/StackExchange.Redis@3.1.0...3.1.3
v3.1.0Compare Source
What's Changed
This is a major feature, with extensive documentation.
Note that it currently has an
[Experimental]marker, linking here, but: this is purely for an abundance of caution; it is considered released and fully supported.(engineering)
available on NuGet
Full Changelog: StackExchange/StackExchange.Redis@3.0.25...3.1.0
v3.0.25Compare Source
What's Changed
New Contributors
Full Changelog: StackExchange/StackExchange.Redis@3.0.17...3.0.25
v3.0.17Compare Source
What's Changed
New Contributors
Full Changelog: StackExchange/StackExchange.Redis@3.0.11...3.0.17
v3.0.11Compare Source
What's Changed
ReadOnlySequence<byte>withRedisValueby @pairbit in #3112RedisValue/ reader logic by using canonical parser and new ShortBlob storage kind by @mgravell in #3114Full Changelog: StackExchange/StackExchange.Redis@3.0.7...3.0.11
v3.0.7Compare Source
What's Changed
MemoryPool<byte>sources for request/response buffering by @mgravell in #3107ConfigurationOptions.RequestBufferPoolandConfigurationOptions.ResponseBufferPoolFull Changelog: StackExchange/StackExchange.Redis@3.0.0_main...3.0.7
v3.0.0Compare Source
3.0.0 represents an overhaul of the internal IO logic, for both performance and stability reasons.
Intentionally, there are no† API changes in this release; it is a direct mirror of 2.13.17, but with the new IO core.
† addendum, one change discovered:
Execute[Async]now detects and respects "admin" commands, i.e. those protected byAllowAdmin; for example, in 2.x,db.Execute("FLUSHALL");would work even ifAllowAdminwas not enabled - this will now throw at the client without issuing the command to the serverWhat is the aim of the internals rewrite?
SE.Redis v2 made use of a few concepts internally:
v3 fundamentally revises these engineering decisions:
This allows for significant performance improvement, especially when processing large / complex results - for example, if we use the
LRANGE_600test fromredis-benchmark(orresp-benchmark):### classic SE.Redis 2.13.17.28173 ### LRANGE_600: 7,579 requests per second LRANGE_600: 7,554 requests per second LRANGE_600: 7,284 requests per second LRANGE_600: 7,158 requests per second LRANGE_600: 7,174 requests per secondvs
### classic SE.Redis 3.0.0.11234 ### LRANGE_600: 16,408 requests per second LRANGE_600: 17,681 requests per second LRANGE_600: 17,331 requests per second LRANGE_600: 17,317 requests per second LRANGE_600: 16,665 requests per second(for tests with simpler results, like
INCR, results of over 1M requests per second are achievable)3.0 is the first part of a wave of planned IO work; 3.1 will revise the "write" part of the write loop, moving message serialization out of the critical serialized core of the multiplexer. All of this work is based on extensive prototyping and benchmarking, demonstrating that these approaches, when combined, provide significant throughput and stability improvements.
This release has undergone extensive testing. If you experience problems, please let us know!
v2.13.17Compare Source
What's Changed
New Contributors
Full Changelog: StackExchange/StackExchange.Redis@2.13.10...2.13.17
v2.13.10Compare Source
This release is marked inactive due to a critical bug when using TCP keep-alives on DNS (i.e. named, not IP) endpoints; this is specific to non-Windows platforms, before .NET 10. See #3086 and #3090
What's Changed
ConfigurationOptions: don't serialize (ToString()) or cloneProtocolif it comes from the defaults-provider by @mgravell in #3082Full Changelog: StackExchange/StackExchange.Redis@2.13.1...2.13.10
Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.