blog.git

blog

~ Personal research notes. blog.sqzer.com
git clone https://github.com/debuman/blog.git
commit 29c40923b2cce5f862de8ba642805499ade4a03e
parent fcb32e5626e70505eca05774cee7d59ae6c5532d
Author: sqzer <110329244+sqzer-x@users.noreply.github.com>
Date: Thu, 24 Sep 2026 12:17:40 +0900

fix: stop CI from restoring stale rendered HTML

withastro/action caches node_modules/.astro by default, and that store
holds every post's rendered HTML keyed only by the .md file's digest.
Restored from the previous run, it ships the old HTML after a change to
a Markdown plugin, a baked diagram or an image, while build-info.json
reports the new commit. It also keeps a failed render failed without
logging the error again.

A cold content build costs under a second.

Diffstat:
M.github/workflows/deploy.yml | 6++++++
1 file changed, 6 insertion(+), 0 deletion(-)

diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml
@@ -26,6 +26,12 @@ jobs:
           # Must go through npm run build so that prebuild — the content gate — runs.
           # Calling astro build directly would skip it.
           build-cmd: npm run build
+          # The action caches node_modules/.astro by default, and that store holds each
+          # post's rendered HTML keyed only by the .md file's digest. Restored, it ships the
+          # old HTML after a change to a Markdown plugin, a diagram or an image, and it keeps
+          # a failed render failed without logging it again. A cold content build costs
+          # under a second.
+          cache: false
         env:
           # Raise to `all` once decks and tags are backfilled, and do not lower it again.
           CONTENT_STRICT: urls,schema