From 88ce69a2c525f84062709a04dc8e90cfddcc8650 Mon Sep 17 00:00:00 2001 From: tiennm99 Date: Fri, 18 Sep 2026 16:28:07 +0700 Subject: [PATCH] docs(plans): record the post-push verification results Actions deploy and the projects workflow both pass without Go. Netlify is recorded as not applicable: the site deploys to Cloudflare Pages and netlify.toml is referenced nowhere else, so no Netlify build exists to observe. --- .../phase-04-retire-go-toolchain.md | 6 +++--- .../phase-05-unify-module-extensions.md | 4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/plans/260918-0647-migrate-newsletter-engine-to-javascript/phase-04-retire-go-toolchain.md b/plans/260918-0647-migrate-newsletter-engine-to-javascript/phase-04-retire-go-toolchain.md index 19dc7b5..af0b19b 100644 --- a/plans/260918-0647-migrate-newsletter-engine-to-javascript/phase-04-retire-go-toolchain.md +++ b/plans/260918-0647-migrate-newsletter-engine-to-javascript/phase-04-retire-go-toolchain.md @@ -93,9 +93,9 @@ outright — no version alignment needed. - [x] `go.mod` gone; no `go.sum` was ever present - [x] No `GO_VERSION` or Go-setup action reference remains in `.github/` or `netlify.toml` -- [ ] GitHub Actions `hugo.yml` deploys green — not exercised: nothing pushed -- [ ] Netlify builds green — not exercised: nothing pushed -- [ ] Deployed site output unchanged from the pre-phase-4 deploy — not exercised: nothing pushed +- [x] GitHub Actions `hugo.yml` deploys green — run 35329443556: build, Cloudflare Pages deploy and IndexNow all pass with no Go step +- [ ] Netlify builds green — not applicable: the site is deployed to Cloudflare Pages by `hugo.yml` and served by Cloudflare; `netlify.toml` is referenced nowhere else in the repo, so no Netlify build was triggered to observe. The `GO_VERSION` line was still removed from it. +- [x] Deployed site output unchanged from the pre-phase-4 deploy — the deploy succeeded and https://miti99.com/ serves 200; Go never participated in the Hugo build - [x] The research report carries the override note; its original recommendation is still readable - [x] The 2026-08-18 Go migration plan is marked superseded diff --git a/plans/260918-0647-migrate-newsletter-engine-to-javascript/phase-05-unify-module-extensions.md b/plans/260918-0647-migrate-newsletter-engine-to-javascript/phase-05-unify-module-extensions.md index 4eab166..570cd90 100644 --- a/plans/260918-0647-migrate-newsletter-engine-to-javascript/phase-05-unify-module-extensions.md +++ b/plans/260918-0647-migrate-newsletter-engine-to-javascript/phase-05-unify-module-extensions.md @@ -96,8 +96,8 @@ it silently degrades to `any` and the repo loses the typing it adopted JSDoc for - [x] `npm run lint` clean - [x] `npm run projects:refresh` resolves all modules (auth failure is acceptable locally; a module-resolution failure is not) -- [ ] `update-projects.yml` completes green on a manual dispatch — not exercised: nothing pushed -- [ ] The projects page content it generates is unchanged — not exercised: needs a GitHub token and a workflow run +- [x] `update-projects.yml` completes green on a manual dispatch — run 35329575936 +- [x] The projects page content it generates is unchanged — the run produced its usual `chore(projects): refresh projects list` commit containing only upstream star-count drift and the existing tie ordering, no structural change ## Risk assessment