Remove dead permanent key from redirect entries

[marcleblanc2]

Follow-up to 7a81737 (#1430), which deleted the commented-out redirects() block from next.config.js.

Why

permanent on redirect entries has been dead data since 578a3ae (#880, Jan 2025) moved redirects into src/middleware.ts. The middleware only reads source and destination, and calls NextResponse.redirect() with no status, so every redirect is a 307 regardless of the field:

const redirect = updatedRedirectsData.find((r: any) => r.source === pathWithoutBase);
if (redirect) {
    return NextResponse.redirect(createRedirectUrl(request, redirect.destination, path));
}

The field was only functional while Next's built-in redirects() consumed the list (cfeed16, Dec 2023 → 578a3ae, Jan 2025). Nothing has read it since, which is why five entries added in #1620 with the key misspelled as permanant went unnoticed.

What

• Remove permanent / permanant from all 1325 entries in src/data/redirects.ts
• Remove the permanent: redirect.permanent pass-through in updatedRedirectsData
• No behaviour change: matching and destinations are untouched

Verification

• rg -o "^\t\t\w+:" src/data/redirects.ts | sort | uniq -c → 1325 source, 1325 destination, nothing else
• npx tsc --noEmit reports no errors in redirects.ts or middleware.ts (the remaining errors are the pre-existing missing contentlayer/generated build output)
• prettier --check on redirects.ts fails the same way it does on main (line-join nits at exactly 80 chars); left as-is to avoid unrelated churn

If we ever want 308s back, the fix is in middleware.ts (pass a status to NextResponse.redirect), and at that point the key can be reintroduced with the entries that actually need it.

[vercel]

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

Project	Deployment	Actions	Updated
sourcegraph-docs	Ready	Preview	Sep 6, 2026 6:31am UTC