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

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
StackExchange.Redis (source)	2.9.17 → 2.11.0

---

Release Notes

StackExchange/StackExchange.Redis (StackExchange.Redis)

v2.11.0

Compare Source

get 2.11.0 on NuGet

What's Changed

For Redis 8.6:

• (docs) Add support for idempotent streams by @​mgravell in #​3006
• (docs) Add support for HOTKEYS by @​mgravell in #​3008
• (docs) Add documentation for client certificate authentication by @​mgravell in #​3009

The time-series changes for 8.6 are over in NRedisStack 1.3.0

Other features:

• (docs) Add support for keyspace notifications including cluster support by @​mgravell in #​2995
• Update README to include Azure Managed Redis by @​redis-phil in #​3005

Internal bits:

• Options: Split out AMR to its own options provider by @​NickCraver in #​2986
• Update CI to 8.6 by @​mgravell in #​3010

New Contributors

• @​redis-phil made their first contribution in #​3005

Full Changelog: StackExchange/StackExchange.Redis@2.10.14...2.11.0

v2.10.14

Compare 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

• fix: Handle Backlog Processor Startup Failures by @​nathan-miller23 in #​3002
• fix: Propagate PhysicalBridge backlog to ServerCounters by @​nathan-miller23 in #​2996
• fix incorrect debug assertion in HGETEX; no impact to release build by @​mgravell in #​2999
• (eng) CI trivia - docker image, codeql, enable manual CI runs (@​mgravell)

New Contributors

• @​nathan-miller23 made their first contribution in #​2996

Full Changelog: StackExchange/StackExchange.Redis@2.10.1...2.10.14

v2.10.1

Adds support for Redis 8.4 features

• support multi-string-set with expiration MSETEX ...; details controlled via new Expiration API
• support checked string-set SET ... IFEQ/IFNE/IFDEQ/IFDNE digestOrValue; details controlled via new ValueCondition API; also uses Expiration for expiry
• support checked string-delete DELEX ... IFEQ/IFNE/IFDEQ/IFDNE digestOrValue (again via ValueCondition)
• use checked string-set/delete to implement LockExtend[Async]/LockRelease[Async] when possible
• support XREADGROUP ... CLAIM minIdleTime for simplified stream processing

Note that niche StringSet[Async] scenarios may require trivial build changes due to removing default parameter values; this simplify means explicitly specifying keepTtl, or using the new Expiration API. 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

• docker image: use client-libs-test by @​mgravell in #​2976
• Support MSETEX by @​mgravell in #​2977
• propose support for XREADGROUP CLAIM by @​mgravell in #​2972
• Support 8.4 CAS/CAD (IF*) operations by @​mgravell in #​2978
• Combine fixups from 8.4 changes by @​mgravell in #​2979

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

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

---

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 becomes conflicted, 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.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud