Update dependency StackExchange.Redis to 2.11.0#1152
Open
renovate[bot] wants to merge 1 commit intodev8from
Open
Update dependency StackExchange.Redis to 2.11.0#1152renovate[bot] wants to merge 1 commit intodev8from
renovate[bot] wants to merge 1 commit intodev8from
Conversation
70c04d6 to
9264bab
Compare
9264bab to
76fc0c4
Compare
76fc0c4 to
4fdeba9
Compare
4fdeba9 to
ee85ce2
Compare
ee85ce2 to
18a55d2
Compare
18a55d2 to
bb5704b
Compare
bb5704b to
1b8fda7
Compare
1b8fda7 to
46ac946
Compare
46ac946 to
67cd772
Compare
bcba33e to
2a86407
Compare
2a86407 to
f88503c
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.8.37→2.11.0Release Notes
StackExchange/StackExchange.Redis (StackExchange.Redis)
v2.11.0Compare Source
get 2.11.0 on NuGet
What's Changed
For Redis 8.6:
HOTKEYSby @mgravell in #3008The time-series changes for 8.6 are over in NRedisStack 1.3.0
Other features:
Internal bits:
New Contributors
Full Changelog: StackExchange/StackExchange.Redis@2.10.14...2.11.0
v2.10.14Compare Source
Priority: high; the backlog fix (#3002) is rare and niche (specific to low-memory scenarios), but fixes a problem where the client can get into a non-recoverable state.
What's Changed
HGETEX; no impact to release build by @mgravell in #2999New Contributors
Full Changelog: StackExchange/StackExchange.Redis@2.10.1...2.10.14
v2.10.1Adds support for Redis 8.4 features
MSETEX ...; details controlled via newExpirationAPISET ... IFEQ/IFNE/IFDEQ/IFDNE digestOrValue; details controlled via newValueConditionAPI; also usesExpirationfor expiryDELEX ... IFEQ/IFNE/IFDEQ/IFDNE digestOrValue(again viaValueCondition)LockExtend[Async]/LockRelease[Async]when possibleXREADGROUP ... CLAIM minIdleTimefor simplified stream processingNote that niche
StringSet[Async]scenarios may require trivial build changes due to removing default parameter values; this simplify means explicitly specifyingkeepTtl, or using the newExpirationAPI. There is no impact to already compiled code (no methods have been removed).8.4 also includes "hybrid search"; this is not currently exposed in SE.Redis, and will be added to NRedisStack ASAP.
What's Changed
Full Changelog: StackExchange/StackExchange.Redis@2.9.32...2.10.1
v2.9.32Compare Source
What's Changed
Full Changelog: StackExchange/StackExchange.Redis@2.9.25...2.9.32
v2.9.25Compare Source
IMPORTANT: this release changes the distribution of pub/sub channels when using cluster; see 2.9.24 for more details.
What's Changed
This change is a critical fix that fixes a packaging failure in 2.9.24; for the relevant feature changes: see 2.9.24.
Full Changelog: StackExchange/StackExchange.Redis@2.9.24...2.9.25
v2.9.24Compare Source
IMPORTANT: this release changes the distribution of pub/sub channels when using cluster:
(this change is specific to pub/sub with regular
SUBSCRIBEchannels, not "sharded"SSUBSCRIBEchannels)SSUBSCRIBE)SSUBSCRIBEchannels are now randomly distributed to nodes by default, but can optionally use key-like routing by calling.WithKeyRouting()on theRedisChannelvalueThis change represents a safer, "least surprises" default; most people expect their cluster to help distribute load, including pub/sub load, between nodes. This is especially useful when there are few (or even only a single) channel(s) that dominate the pub/sub load, which is surprisingly common. Without this change, all that load would be handled only by a single server, because the channel
my_notificationswould be treated similarly to a key, via hash-slot sharding, and all clients would connect to the node serving that slot - when in reality, any node can be used for subscription, with the server distributing events horizontally to all nodes.If you prefer the routed behaviour: use
.WithKeyRouting()before subscribing.What's Changed
SSUBSCRIBE) routing to random, with newWithKeyRouting()API to opt into routed by @mgravell in #2958New Contributors
Full Changelog: StackExchange/StackExchange.Redis@2.9.17...2.9.24
v2.9.17Compare Source
What's Changed
sealed) and fix warnings for it by @Henr1k80 in #2942Full Changelog: StackExchange/StackExchange.Redis@2.9.11...2.9.17
v2.9.11Compare Source
What's Changed
HGETDEL,HGETEXandHSETEXsupport (#2863 by atakavci)Condition.SortedSet[Not]ContainsStartingcondition for transactions (#2638 by ArnoKoll)XPENDING IDLEtime filter (#2822 by david-brink-talogy)GetServer(RedisKey, ...)API (#2936 by mgravell)doubleformatting performance on net8+ and fix equality incorrectness re special doubles by @mgravell in #2928SetIntersectionLengthandSortedSet{Combine[WithScores]|IntersectionLength}(#2863 by mgravell)StreamAddmessage (#2941 by mgravell)New Contributors
Full Changelog: StackExchange/StackExchange.Redis@2.8.58...2.9.11
v2.8.58Compare Source
What's Changed
New Contributors
Full Changelog: StackExchange/StackExchange.Redis@2.8.47...2.8.58
v2.8.47Compare Source
What's Changed
Full Changelog: StackExchange/StackExchange.Redis@2.8.41...2.8.47
v2.8.41Compare Source
What's Changed
Sharded pub/sub operations are where the pub/sub channels are distributed over a multi-node redis cluster using similar slot rules to keys; all such operations (for both "pub" and "sub") must be communicated to the correct node. This contrasts to regular/legacy pub/sub where you can "pub" or "sub" to any node, and the message is broadcast horizontally via all nodes in the cluster. To use sharded operations, use the
RedisChannel.ShardedAPI when constructing channels. There is no concept of pattern-based sharded pub/sub.Full Changelog: StackExchange/StackExchange.Redis@2.8.37...2.8.41
Configuration
📅 Schedule: Branch creation - "before 1am,before 5am,before 9am" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.