Retroactively update changelog redirects to support new changelog structure

[mvvmm]

Summary

• Add pagination to changelog #28527 created some double redirect chains with existing changelog redirects. This PR fixes those

Documentation checklist

• Files which have changed name or location have been allocated redirects.

[github-actions]

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern	Owners
/public/__redirects	@cloudflare/content-engineering, @cloudflare/pcx-technical-writing

[github-actions]

Preview URL: https://43969c2a.preview.developers.cloudflare.com
Preview Branch URL: https://fix-changelog-redirect-chains.preview.developers.cloudflare.com

[mvvmm]

/bonk Please check that this PR fixes all the double redirects regarding the changelog posts and their new location: /changelog/post/...

[ask-bonk]

Review: Double Redirect Fix

I verified all 37 changed redirect targets in this PR against the full __redirects file (2594 lines). The analysis confirms this PR correctly fixes all double redirect chains created by #28527.

What was broken

PR #28527 moved individual changelog posts from /changelog/{slug}/ to /changelog/post/{slug}/ and added wildcard rules:

/changelog/2024-* /changelog/post/2024-:splat 301
/changelog/2025-* /changelog/post/2025-:splat 301
/changelog/2026-* /changelog/post/2026-:splat 301

However, 37 existing explicit redirects still pointed to /changelog/{slug}/ (without /post/), creating double redirect chains:

• /waf/change-log/2025-01-06/ → /changelog/2025-01-06-waf-release/ → (wildcard) → /changelog/post/2025-01-06-waf-release/
• /changelog/fundamentals/... → /changelog/2025-... → (wildcard) → /changelog/post/2025-...

What this PR fixes

• 26 WAF change-log rules: All updated to target /changelog/post/... directly
• 10 fundamentals/terraform rules: All updated to target /changelog/post/... directly
• 1 terraform year-typo rule: Updated to target /changelog/post/... directly

Verification results

• Zero redirect destinations match /changelog/20XX-* (would trigger wildcard double-hop)
• Zero changelog-related destinations also appear as sources (no chains)
• All 37 targets now point directly to /changelog/post/..., the final canonical location

Minor note (not blocking)

There is one pre-existing theoretical double redirect path: /changelog-next/* → /changelog/:splat (line 2402). If someone visited /changelog-next/2025-something/, it would first redirect to /changelog/2025-something/ then the wildcard would redirect to /changelog/post/2025-something/. This is pre-existing and outside this PR's scope — and the changelog-next path was unlikely to have date-prefixed subpaths.

LGTM — this correctly eliminates all double redirect chains.

[ask-bonk]

Review posted. Here's the summary:

PR #28605 correctly fixes all double redirect chains. I verified all 37 changes against the full __redirects file (2594 lines):

• 26 WAF change-log rules -- all updated from /changelog/YYYY-* to /changelog/post/YYYY-*
• 10 fundamentals/terraform rules -- all updated similarly
• 1 terraform year-typo rule -- updated similarly

After the PR, zero redirect destinations match the wildcard pattern /changelog/20XX-*, meaning no double-hop chains remain. The PR is approved.

github run