chore(deps): update dependency stackexchange.redis to 2.9.32

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
StackExchange.Redis (source)	2.9.11 -> 2.9.32

---

Release Notes

StackExchange/StackExchange.Redis (StackExchange.Redis)

v2.9.32

Compare Source

What's Changed

• Fix sharded pub/sub handling over slot migrations by @​mgravell in #​2969
• (build) "actions": support publishing to MyGet off main branch by @​NickCraver in #​2964
• (build) Update CI badge by @​mgravell in #​2967

Full Changelog: StackExchange/StackExchange.Redis@2.9.25...2.9.32

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

• eng: remove PublicSign windows-only restriction by @​mgravell in #​2963

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.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

• Fix 2951 - Sentinel reconnect failure by @​mgravell in #​2956
• Remove supported Envoyproxy commands from exclusions. by @​sshumakov in #​2957
• Convert to Hex only on Encoding.UTF8.GetString possible exceptions by @​jcaspes in #​2954
• eng: prefer Volatile.Read over Thread.VolatileRead by @​mgravell in #​2960
• Channel routing: revert normal (non-SSUBSCRIBE) routing to random, with new WithKeyRouting() API to opt into routed by @​mgravell in #​2958

New Contributors

• @​sshumakov made their first contribution in #​2957
• @​jcaspes made their first contribution in #​2954

Full Changelog: StackExchange/StackExchange.Redis@2.9.17...2.9.24

v2.9.17

Compare Source

What's Changed

• Add vector-set support by @​mgravell in #​2939
• fix: RedisValue/RedisResult: cast to double should respect special values by @​mgravell in #​2950
• Internals:
  • Enable CA1852 (sealed) and fix warnings for it by @​Henr1k80 in #​2942
  • Flush & write concurrently in LoggingTunnel and avoid double lookups in dictionaries by @​Henr1k80 in #​2943

Full Changelog: StackExchange/StackExchange.Redis@2.9.11...2.9.17

---

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.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.