Hopefully fix vercel deploy

[martinbonnin]

Vercel deploys are broken since #2448

LLM analysis:

Vercel caches the pnpm virtual store between deployments. When the nextra patch hash changes (old: a4cb9ca3... → new: 524e6c4e...), Vercel's cached node_modules still has nextra
  installed with the old patch (which only had || metaKey === 'conf'). The new _meta.tsx adds a day entry that requires || metaKey === 'day' in the patch — without the new patch applied, nextra throws
  a validation error during build.

  The "lock files" angle is accurate in the sense that pnpm identifies the installed nextra by its patch hash, and the hash mismatch between cache and new lockfile is the trigger.

  Fixes:

  1. Immediate (no code change needed): In the Vercel dashboard, go to the failing deployment → "Redeploy" → make sure "Use existing Build Cache" is unchecked / invalidate the build cache. This forces
  Vercel to reinstall with the new patch.
  2. Code fix (more robust): Change route: "/day" to href: "/day" in _meta.tsx. This makes nextra's original validation pass without needing the patch workaround (the check is metaItem.href, which route
  doesn't satisfy but href does). That would also let you remove || metaKey === 'day' from the patch. Note that conf has the same pattern — if you wanted consistency, both could use href. The tradeoff
  is that href vs route might differ in how nextra computes the "active" state for the nav item.

I'm a bit out of my comfort zone here but that sounds reasonnable. Let me know otherwise.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
graphql-github-io	Ready	Preview, Comment	Jun 25, 2026 6:01pm