Pin portal v0.3.1 - content-hashed assets (LEPTOS_HASH_FILES=true)
Deploy instance / deploy (push) Successful in 1s
Lint and reload / lint (push) Successful in 2s
Lint and reload / reload (push) Successful in 0s

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Bendik Aagaard Lynghaug
2026-08-25 19:51:29 +02:00
co-authored by Claude Fable 5
parent 87d004cc05
commit 58b03a222e
+5 -1
View File
@@ -18,7 +18,7 @@ on:
- .gitea/workflows/deploy.yml - .gitea/workflows/deploy.yml
env: env:
PORTAL_RELEASE: v0.3.0 PORTAL_RELEASE: v0.3.1
INSTANCE: uhhm-portal INSTANCE: uhhm-portal
jobs: jobs:
@@ -68,6 +68,10 @@ jobs:
# The release tarball carries the site bundle at site/ (no # The release tarball carries the site bundle at site/ (no
# target/ prefix), so override Cargo.toml's build-time path. # target/ prefix), so override Cargo.toml's build-time path.
LEPTOS_SITE_ROOT=site LEPTOS_SITE_ROOT=site
# Portal ships content-hashed pkg files (portal.<hash>.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
AUTOMATION_READ_TOKEN=${{ secrets.AUTOMATION_READ_TOKEN }} AUTOMATION_READ_TOKEN=${{ secrets.AUTOMATION_READ_TOKEN }}
# Read-only (read:user,read:repository,read:organization), # Read-only (read:user,read:repository,read:organization),
# used only by the Gitea resource sources (portal # used only by the Gitea resource sources (portal