From 3846fa1b6d4f43d5e5d0d023c554dffeeca2d3af Mon Sep 17 00:00:00 2001
From: Florent Tapponnier <florent.tapponnier@gmail.com>
Date: Fri, 29 May 2026 16:44:26 +0200
Subject: [PATCH] fix: bump outer all-benchmarks cache key to v6

PR #184 added providersPerChain to Benchmark + bumped the inner bench-unfiltered cache key to v4, but missed the OUTER loadAllBenchmarks cache (`all-benchmarks-v5`). The aggregate cache can keep serving v5-era Benchmark slices (no providersPerChain) even after the per-bench cache is fresh, leaving /products/[slug] showing phantom chips for chain-restricted providers.
---
 src/lib/spec.ts | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/src/lib/spec.ts b/src/lib/spec.ts
index a09fb8ce..2df90d39 100644
--- a/src/lib/spec.ts
+++ b/src/lib/spec.ts
@@ -149,7 +149,12 @@ const loadAllBenchmarksCached = unstable_cache(
     }
     return benchmarks.sort((a, b) => a.number.localeCompare(b.number));
   },
-  ["all-benchmarks-v5"],
+  // v6: aggregate cache. Bumped together with bench-unfiltered-v4 so
+  // the per-bench providersPerChain field actually propagates into the
+  // benchmark slice the products page reads. Without bumping this, the
+  // outer cache can keep serving v5-era benchmarks (no providersPerChain)
+  // even after the inner cache is fresh.
+  ["all-benchmarks-v6"],
   { revalidate: 60, tags: ["benchmarks"] },
 );
 export const loadAllBenchmarks = cache(loadAllBenchmarksCached);