From 83f7533c2171e053c07c5b689467da1f3991d1a2 Mon Sep 17 00:00:00 2001 From: Bendik Aagaard Lynghaug Date: Tue, 25 Aug 2026 19:51:30 +0200 Subject: [PATCH] Pin portal v0.3.1 - content-hashed assets (LEPTOS_HASH_FILES=true) Co-Authored-By: Claude Fable 5 --- .gitea/workflows/deploy.yml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.gitea/workflows/deploy.yml b/.gitea/workflows/deploy.yml index a28e523..72ec02d 100644 --- a/.gitea/workflows/deploy.yml +++ b/.gitea/workflows/deploy.yml @@ -18,7 +18,7 @@ on: - .gitea/workflows/deploy.yml env: - PORTAL_RELEASE: v0.3.0 + PORTAL_RELEASE: v0.3.1 INSTANCE: redoal-portal jobs: @@ -67,6 +67,10 @@ jobs: # The release tarball carries the site bundle at site/ (no # target/ prefix), so override Cargo.toml's build-time path. LEPTOS_SITE_ROOT=site + # Portal ships content-hashed pkg files (portal..js) with + # a hash.txt in the site root; this makes the server reference + # them, so a stale cached bundle can never pair with new wasm. + LEPTOS_HASH_FILES=true # Read-only Gitea token - here it also backs the # gitea_releases source for the private redoal/redoal repo, # so the owning user needs read access there.