`/packs` listing appears stale while direct pack pages are already live

[Sogl]

The /packs page appears to be serving a stale snapshot, even though direct pack pages are already live.

Examples of direct pack pages that currently work:

• https://openpeon.com/packs/pulp_fiction
• https://openpeon.com/packs/wc2_peon_ru

But the main listing page still looks stale:

• https://openpeon.com/packs

Observed behavior:

• /packs still reports lastUpdated: 2026-03-12
• newer packs are available by direct URL, but are not reflected correctly in the /packs listing snapshot

What I checked:

• the registry is up to date:
  • https://github.com/PeonPing/registry/blob/main/index.json
• the published registry JSON is also up to date:
  • https://peonping.github.io/registry/index.json
• so this looks like a site-level caching / revalidation issue on /packs, not a registry issue

Relevant code:

• direct pack page:
  • https://github.com/PeonPing/openpeon/blob/main/site/src/app/packs/%5Bname%5D/page.tsx
• listing page:
  • https://github.com/PeonPing/openpeon/blob/main/site/src/app/packs/page.tsx
• registry fetcher:
  • https://github.com/PeonPing/openpeon/blob/main/site/src/lib/registry.ts
• registry rebuild trigger:
  • https://github.com/PeonPing/registry/blob/main/.github/workflows/trigger-openpeon-rebuild.yml

Potential cause:

• the direct pack route explicitly exports revalidate = 1800
• the /packs route does not appear to export revalidate
• fetchAllPacks() uses cached fetches against the published registry index

My guess:

• direct pack pages are revalidating correctly
• /packs is still serving an older prerendered snapshot

If helpful, I can also open a follow-up PR once the intended caching behavior for /packs is confirmed.

[garysheng]

Good catch and excellent diagnosis! You nailed the root cause.

Added export const revalidate = 1800; to /packs/page.tsx in PR #18 (now merged) — this matches the same ISR window used by the per-pack routes. The listing should start revalidating on the correct 30-minute cycle going forward.

Thanks for the detailed writeup and the pointer to the relevant files!