Hanzo Dev
4962beb38b
Its comment told the next person to run `pnpm build && npx wrangler@3 deploy`, which is exactly how the live host ended up months behind main. Deploying is CI now, and CI is the thing that checks the live bytes afterwards. The local command is still there for a break-glass, with the consequence stated. Co-authored-by: Hanzo Dev <[email protected]>
17 lines
628 B
TOML
17 lines
628 B
TOML
# hanzo.sh — assets-only Worker (CF Pages project limit reached; 7stars precedent)
|
|
#
|
|
# Deploying is .github/workflows/deploy.yml, which also re-fetches hanzo.sh and
|
|
# fails unless the live bytes are the ones it just built. Do not publish this by
|
|
# hand: hand-publishing is why the site served an installer months older than
|
|
# main. `npx wrangler@3 deploy` still works locally for a break-glass, but then
|
|
# main and the live host are two different states again — check afterwards.
|
|
name = "hanzo-sh"
|
|
compatibility_date = "2026-07-01"
|
|
|
|
[assets]
|
|
directory = "dist"
|
|
|
|
routes = [
|
|
{ pattern = "hanzo.sh", custom_domain = true }
|
|
]
|