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.Sharded API when constructing channels. There is no concept of pattern-based sharded pub/sub.
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.8.37` -> `2.8.41` |
---
### Release Notes
<details>
<summary>StackExchange/StackExchange.Redis (StackExchange.Redis)</summary>
### [`v2.8.41`](https://github.com/StackExchange/StackExchange.Redis/releases/tag/2.8.41)
[Compare Source](https://github.com/StackExchange/StackExchange.Redis/compare/2.8.37...2.8.41)
#### What's Changed
- Support sharded pubsub commands by [@​mgravell](https://github.com/mgravell) [@​vandyvilla](https://github.com/vandyvilla) [@​atakavci](https://github.com/atakavci) [@​xli](https://github.com/xli) in https://github.com/StackExchange/StackExchange.Redis/pull/2887
[Sharded pub/sub operations](https://redis.io/docs/latest/commands/spublish/) 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.Sharded` API when constructing channels. There is no concept of pattern-based sharded pub/sub.
**Full Changelog**: https://github.com/StackExchange/StackExchange.Redis/compare/2.8.37...2.8.41
</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:eyJjcmVhdGVkSW5WZXIiOiIzOC4xNDIuNyIsInVwZGF0ZWRJblZlciI6IjM4LjE0Mi43IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This PR contains the following updates:
2.8.37->2.8.41Release Notes
StackExchange/StackExchange.Redis (StackExchange.Redis)
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: https://github.com/StackExchange/StackExchange.Redis/compare/2.8.37...2.8.41
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.
This PR has been generated by Renovate Bot.