Skip to content

Regenerate routing artifacts (blog:redirects drift) - #271

Merged
saiyam1814 merged 1 commit into
mainfrom
fix/regenerate-routing-artifacts
Sep 16, 2026
Merged

saiyam1814 merged 1 commit into
mainfrom
fix/regenerate-routing-artifacts

Conversation

@saiyam1814

Copy link
Copy Markdown
Member

scripts/generate-redirects.mjs writes four files. Its committed output had drifted from content/blog:

slug _redirects vercel.json _worker.js
kubernetes-observability-in-2026-with-openobserve (#268) missing missing missing
inside-kueue-how-kubernetes-decides-what-runs-next (#266) ok ok missing

BLOG_SLUGS goes 201 → 203. Produced by running npm run blog:redirects with no manual edits. The diff is purely additive — no line is removed from any of the three files, verified against the previous main.

No live impact

prebuild runs this generator during the Pages build, so the deployed _worker.js is always regenerated and both posts already route correctly today:

200  https://kubesimplify.com/kubernetes-observability-in-2026-with-openobserve
200  https://blog.kubesimplify.com/kubernetes-observability-in-2026-with-openobserve
200  https://blog.kubesimplify.com/inside-kueue-how-kubernetes-decides-what-runs-next

This is a repo-hygiene fix. The value is that the committed artifacts stop disagreeing with content/blog — the drift is exactly why nobody noticed #268 never got its entries.

Worth considering separately

_worker.js is a build artifact whose committed copy is never the one served. Adding it (and _routes.json) to .gitignore, or a CI check that fails when npm run blog:redirects produces a diff, would prevent this recurring. Happy to open that as a follow-up.

🤖 Generated with Claude Code

The committed output of scripts/generate-redirects.mjs had drifted from
content/blog:

- kubernetes-observability-in-2026-with-openobserve (#268) was missing from
  _redirects, vercel.json and _worker.js
- inside-kueue-how-kubernetes-decides-what-runs-next (#266) was missing from
  _worker.js (the PR committed _redirects and vercel.json but not the worker)

BLOG_SLUGS goes 201 -> 203. Nothing is removed; the diff is purely additive.

No live impact: prebuild regenerates all four files during the Pages build, so
both posts already route correctly. This just stops the repo shipping stale
artifacts, which is what made the omission invisible in the first place.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying website with  Cloudflare Pages  Cloudflare Pages

Latest commit: 0c45112
Status: ✅  Deploy successful!
Preview URL: https://7a4a191b.website-dab.pages.dev
Branch Preview URL: https://fix-regenerate-routing-artif.website-dab.pages.dev

View logs

@saiyam1814
saiyam1814 merged commit 0629337 into main Sep 16, 2026
3 checks passed
@saiyam1814
saiyam1814 deleted the fix/regenerate-routing-artifacts branch September 16, 2026 12:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant