-
-
Notifications
You must be signed in to change notification settings - Fork 37
Update dependency StackExchange.Redis to 2.9.32 #295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/stackexchange.redis-2.x
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
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
a6cc802 to
0bc1fed
Compare
0bc1fed to
bc1ef63
Compare
bc1ef63 to
689de81
Compare
750e028 to
cd919b6
Compare
759dc0d to
584e03f
Compare
584e03f to
4651608
Compare
4651608 to
43ecfe6
Compare
43ecfe6 to
0aa6f0c
Compare
0aa6f0c to
f035ca3
Compare
f035ca3 to
102fca8
Compare
102fca8 to
ae82f7f
Compare
ae82f7f to
e636e2f
Compare
e636e2f to
c6c4240
Compare
c6c4240 to
54427b6
Compare
54427b6 to
bfe5618
Compare
bfe5618 to
0504a9c
Compare
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.0->2.9.32Release Notes
StackExchange/StackExchange.Redis (StackExchange.Redis)
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
v2.8.37Compare Source
What's Changed
ConfigurationOptions.SetUserPemCertificate(...)andConfigurationOptions.SetUserPfxCertificate(...)methods to simplify using client certificates (#2873 by @mgravell)AuthenticateAsClientto fully async after dropping older framework support, to help client thread starvation in cases TLS negotiation stalls server-side (#2878 by @NickCraver)New Contributors
Full Changelog: StackExchange/StackExchange.Redis@2.8.31...2.8.37
v2.8.31What's Changed
IReconnectRetryPolicytiming in the case that a node that was present disconnects indefinitely (#2856 by @NickCraver)New Contributors
Full Changelog: StackExchange/StackExchange.Redis@2.8.24...2.8.31
v2.8.24Compare Source
What's Changed
UNWATCH(#2824 by @mgravell)Full Changelog: StackExchange/StackExchange.Redis@2.8.22...2.8.24
v2.8.22Compare Source
What's Changed
4.0.0to6.0.0for Azure Redis resources (#2810 by @philon-msft)Microsoft.Bcl.AsyncInterfacesdependency from5.0.0to6.0.0(#2820 by @NickCraver)Full Changelog: StackExchange/StackExchange.Redis@2.8.16...2.8.22
v2.8.16Compare Source
What's Changed
HeartbeatConsistencyChecksis enabled (#2795 by @NickCraver)Full Changelog: StackExchange/StackExchange.Redis@2.8.14...2.8.16
v2.8.14Compare Source
What's Changed
New Contributors
Full Changelog: StackExchange/StackExchange.Redis@2.8.12...2.8.14
v2.8.12Compare Source
What's Changed
HSCAN NOVALUES(see #2721) (#2722 by @atakavci)CheckInfoReplicationeven withHeartbeatConsistencyChecks(#2784 by @NickCraver and @leachdaniel-clark)New Contributors
Full Changelog: StackExchange/StackExchange.Redis@2.8.0...2.8.12
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 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.