build(deps): bump StackExchange.Redis from 3.2.1 to 3.3.0

[cosmin-staicu]

Stacked on #193 — merge that first. This PR's base is its branch, so the diff shown here is the bump alone.

Summary

StackExchange.Redis 3.2.1 → 3.3.0, which brings 3.2.15 along with it. This repository calls no API either release altered, and the full suite passes on both target frameworks against a live server.

Dependabot proposed 3.2.1 (#192, merged); 3.3.0 landed on 2026-09-18, after that PR was opened.

What is in the range, and whether it reaches us

Upstream change	Reaches us?
#3225 SwitchPrimary retires the servers its rebuild drops	Yes — see below
#3237 IServer.Execute supplies the default database	Yes, but nothing here relies on it
#3191 server-native maintenance notifications	Opt-in; deliberately left off
#3230 RedisValue.EqualityComparer	No use site — nothing here is keyed by RedisValue
#3228 string-vs-blob compare without decoding	Free wherever it applies; no code change
#3224 connection group throws RedisConnectionException	No — no connection groups here
Redis 8.10 bindings / geo-redundant failover out of preview, vector sets no longer experimental	Not used

#3225 is the one that touches our code. A dropped node used to stay in the server snapshot — connected and selectable — and IConnectionMultiplexer.GetServers() reports that snapshot (ConnectionMultiplexer.cs:1608). RedisConnector.GetPrimaries() filters on !IsReplica && IsConnected, which a stale-but-connected primary passes. So on a Sentinel-managed connection the stream maintainer could be handed a node that had left the service, and per the upstream description occasionally the same address twice. Fixed upstream; our de-duplication already handled the second half.

#3237 is upstream's fix for the bug corrected in #193 — IServer.Execute no longer refuses a database-specific command. The maintainer passes the database explicitly, so it neither depends on this nor regresses on earlier versions. Probed on 3.1.31, 3.2.1, 3.2.15 and 3.3.0.

Also

Drops the SER007 suppression in RedisStreamSubjectWriterTests — RedisErrorKind lost its [Experimental] marking in 3.3.0, so the pragma was silencing a diagnostic nothing raises any more. Confirmed by reflecting over both assemblies.

Verification

• Solution builds with 0 warnings.
• Full suite against a live Redis: net10.0 1775/1775, net8.0 1754/1754.
• Re-probed the private members RedisConnector.GetMasterPhysicalConnectionMetrics reflects into (RedisServer.server, ServerEndPoint.interactive, PhysicalBridge.physical, PhysicalConnection.lastWriteTickCount/_writeStatus/lastReadTickCount/_readStatus, GetSentAwaitingResponseCount) — all still resolve on 3.3.0. Green CI would not have caught a break here: that method is [ExcludeFromCodeCoverage] and only runs against a live multiplexer.
• IServer.ClusterConfiguration still returns a fresh instance per refresh, so the ReferenceEquals contract RefreshClusterMembershipAsync depends on holds.

Contributor declaration

• I signed off my commits per the DCO (git commit -s).
• I am contributing on behalf of my employer, or in the course of employment / using employer resources.

[Copilot]

Copilot review overview

🟢 Approval recommended

The only noted issue is a minor changelog clarification.

Review effort: Lite
Findings: None

What changed in this PR

Updates StackExchange.Redis from 3.2.1 to 3.3.0 and removes an obsolete warning suppression.

Changes:

• Bumps the centrally managed Redis dependency.
• Removes the local SER007 suppression.
• Documents upgrade impacts and verification.

File	Description
Directory.Packages.props	Updates StackExchange.Redis to 3.3.0.
tests/​UiPath.Caching.Tests/​Broadcast/​RedisStreamSubjectWriterTests.cs	Removes the obsolete SER007 suppression.
CHANGELOG.md	Records the dependency upgrade and related upstream changes.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.