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

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
StackExchange.Redis (source)	nuget	patch	2.12.4 → 2.12.8

---

Release Notes

StackExchange/StackExchange.Redis (StackExchange.Redis)

v2.12.8

Compare Source

What's Changed

• Filter out 'temporary placeholder' cluster nodes with a handshake flag by @​TimLovellSmith in #​3043
• Support multi-DB cluster usage on valkey by @​mgravell in #​3040
• Implement GRCA by @​mgravell in #​3041

Full Changelog: StackExchange/StackExchange.Redis@2.12.4...2.12.8

---

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.

[claude]

Code Review: Dependency Update

This is a routine Renovate bot patch update for StackExchange.Redis from 2.12.4 → 2.12.8.

Changes

• Directory.Packages.props: Central package version bump
• examples/CloudShop/CloudShop.Tests/CloudShop.Tests.csproj: Direct reference update (this project does not use central package management for this dependency)

Assessment

The changes are correct and minimal. Patch version bumps in StackExchange.Redis typically include bug fixes and stability improvements — in this case:

• Filtering out 'temporary placeholder' cluster nodes with handshake flag
• Multi-DB cluster usage support on Valkey
• GRCA implementation

Observations

The CloudShop.Tests.csproj has a direct PackageReference with a hardcoded version rather than deferring to Directory.Packages.props. This inconsistency means Renovate must update the version in two places instead of one. Consider migrating this reference to use the central package version (remove the Version attribute from the PackageReference so it picks up from Directory.Packages.props), which would simplify future dependency updates to a single-line change.

This is a low-priority improvement and not a blocker for merging — the update itself is safe to approve.

✅ Approved for merge.