training/voting-example
2
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

Update dependency StackExchange.Redis to 2.9.25 #281

Merged
renovate merged 1 commits from renovate/stackexchange.redis-2.x into main 2025-10-05 00:41:52 +00:00
Conversation 0 Commits 1 Files Changed 1 +1 -1
renovate commented 2025-10-05 00:41:49 +00:00
Member
Copy Link

This PR contains the following updates:

Package Type Update Change
StackExchange.Redis (source) nuget patch 2.9.17 -> 2.9.25

Release Notes

StackExchange/StackExchange.Redis (StackExchange.Redis)

v2.9.25

Compare 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: https://github.com/StackExchange/StackExchange.Redis/compare/2.9.24...2.9.25

v2.9.24

Compare Source

IMPORTANT: this release changes the distribution of pub/sub channels when using cluster:

(this change is specific to pub/sub with regular SUBSCRIBE channels, not "sharded" SSUBSCRIBE channels)

  • pre 2.9.24: all channels would always be routed similarly to key-like routing (and similar to SSUBSCRIBE)
  • from 2.9.24: non-SSUBSCRIBE channels are now randomly distributed to nodes by default, but can optionally use key-like routing by calling .WithKeyRouting() on the RedisChannel value

This 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_notifications would 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

New Contributors

Full Changelog: https://github.com/StackExchange/StackExchange.Redis/compare/2.9.17...2.9.24

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [StackExchange.Redis](https://stackexchange.github.io/StackExchange.Redis/) ([source](https://github.com/StackExchange/StackExchange.Redis)) | nuget | patch | `2.9.17` -> `2.9.25` | --- ### Release Notes <details> <summary>StackExchange/StackExchange.Redis (StackExchange.Redis)</summary> ### [`v2.9.25`](https://github.com/StackExchange/StackExchange.Redis/releases/tag/2.9.25) [Compare Source](https://github.com/StackExchange/StackExchange.Redis/compare/2.9.24...2.9.25) IMPORTANT: this release changes the distribution of pub/sub channels when using cluster; see [2.9.24](https://github.com/StackExchange/StackExchange.Redis/releases/tag/2.9.24) for more details. #### What's Changed - eng: remove PublicSign windows-only restriction by [@&#8203;mgravell](https://github.com/mgravell) in https://github.com/StackExchange/StackExchange.Redis/pull/2963 This change is a critical fix that fixes a packaging failure in [2.9.24](https://github.com/StackExchange/StackExchange.Redis/releases/tag/2.9.24); for the relevant *feature* changes: see [2.9.24](https://github.com/StackExchange/StackExchange.Redis/releases/tag/2.9.24). **Full Changelog**: https://github.com/StackExchange/StackExchange.Redis/compare/2.9.24...2.9.25 ### [`v2.9.24`](https://github.com/StackExchange/StackExchange.Redis/releases/tag/2.9.24) [Compare Source](https://github.com/StackExchange/StackExchange.Redis/compare/2.9.17...2.9.24) IMPORTANT: this release changes the distribution of pub/sub channels when using cluster: (this change is specific to pub/sub with regular `SUBSCRIBE` channels, not "sharded" `SSUBSCRIBE` channels) - pre 2.9.24: all channels would always be routed similarly to key-like routing (and similar to `SSUBSCRIBE`) - from 2.9.24: non-`SSUBSCRIBE` channels are now randomly distributed to nodes by default, but can *optionally* use key-like routing by calling `.WithKeyRouting()` on the `RedisChannel` value This 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_notifications` would 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 - Fix 2951 - Sentinel reconnect failure by [@&#8203;mgravell](https://github.com/mgravell) in https://github.com/StackExchange/StackExchange.Redis/pull/2956 - Remove supported Envoyproxy commands from exclusions. by [@&#8203;sshumakov](https://github.com/sshumakov) in https://github.com/StackExchange/StackExchange.Redis/pull/2957 - Convert to Hex only on Encoding.UTF8.GetString possible exceptions by [@&#8203;jcaspes](https://github.com/jcaspes) in https://github.com/StackExchange/StackExchange.Redis/pull/2954 - eng: prefer Volatile.Read over Thread.VolatileRead by [@&#8203;mgravell](https://github.com/mgravell) in https://github.com/StackExchange/StackExchange.Redis/pull/2960 - Channel routing: revert normal (non-`SSUBSCRIBE`) routing to random, with new `WithKeyRouting()` API to opt into routed by [@&#8203;mgravell](https://github.com/mgravell) in https://github.com/StackExchange/StackExchange.Redis/pull/2958 #### New Contributors - [@&#8203;sshumakov](https://github.com/sshumakov) made their first contribution in https://github.com/StackExchange/StackExchange.Redis/pull/2957 - [@&#8203;jcaspes](https://github.com/jcaspes) made their first contribution in https://github.com/StackExchange/StackExchange.Redis/pull/2954 **Full Changelog**: https://github.com/StackExchange/StackExchange.Redis/compare/2.9.17...2.9.24 </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS40My41IiwidXBkYXRlZEluVmVyIjoiNDEuNDMuNSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==-->
renovate added 1 commit 2025-10-05 00:41:50 +00:00
Update dependency StackExchange.Redis to 2.9.25 4dbcbadc92
renovate scheduled this pull request to auto merge when all checks succeed 2025-10-05 00:41:50 +00:00
renovate merged commit bb8e6a2946 into main 2025-10-05 00:41:52 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
marco renovate
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: training/voting-example#281
Delete Branch "renovate/stackexchange.redis-2.x"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?