From d6fdcd0bce4d27fcfefb280e095958540ac2ef61 Mon Sep 17 00:00:00 2001 From: Bendik Aagaard Lynghaug Date: Tue, 25 Aug 2026 19:52:31 +0200 Subject: [PATCH] README: hashed pkg assets in the release flow Co-Authored-By: Claude Fable 5 --- README.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 38f2738..e59fc04 100644 --- a/README.md +++ b/README.md @@ -105,7 +105,10 @@ cargo release patch # or minor / major That bumps `Cargo.toml`, tags `v`, and pushes; CI (`.gitea/workflows/publish.yml`) reacts to the tag, builds once, and attaches `portal-v.tar.gz` (`portal` + `question_lint` + -`site/`) to the Gitea release. Plain pushes to `main` only run the +`hash.txt` + `site/`) to the Gitea release. Pkg files are +content-hashed (`hash-files = true`; instances run with +`LEPTOS_HASH_FILES=true`), so a freshly served page can never pair a +stale cached bundle with new wasm. Plain pushes to `main` only run the tests (`test.yml`) — nothing reaches production from this repo. **Roll it out** (in a content repo): edit one line in that repo's