chore(deps): bump crossbeam-epoch to 0.9.20 (RUSTSEC-2026-0204)

[pbeza]

cargo deny advisories are failing repo-wide (on main and open PRs) on RUSTSEC-2026-0204 — an invalid pointer dereference in crossbeam-epoch 0.9.18's fmt::Pointer impl, reached transitively via near-store.

Bumps the lockfile to the fixed 0.9.20 (semver-compatible patch; lockfile-only, no manifest change).

Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0204

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[claude]

Pull request overview

Lockfile-only bump of crossbeam-epoch from 0.9.18 → 0.9.20 to remediate RUSTSEC-2026-0204 (invalid pointer dereference in the fmt::Pointer impl), which was failing cargo deny repo-wide. crossbeam-epoch is pulled in transitively via near-store; there is no direct usage in this workspace's manifests or source, and the bump is a semver-compatible patch, so risk is minimal.

Changes:

• Bump crossbeam-epoch to 0.9.20 in Cargo.lock (checksum updated accordingly).

Reviewed changes

Per-file summary

File	Description
Cargo.lock	Patch bump of crossbeam-epoch 0.9.18 → 0.9.20 with corresponding checksum update.

Findings

No blocking or non-blocking issues. Verified:

• No direct references to crossbeam-epoch / crossbeam_epoch in any Cargo.toml or .rs file in the workspace — usage is purely transitive.
• The change is confined to Cargo.lock (no manifest edits).
• 0.9.18 → 0.9.20 is a semver-compatible patch update within the same minor line.

✅ Approved