papers.hanzo.ai publishes its static export from main: site: writes s3://hanzo-sites/hanzo/papers, the prefix its route serves. Without it CI built the image and published nothing.
Hanzo CI/CD / test (linux-amd64) (push) Skipped
Hanzo CI/CD / test (linux-arm64) (push) Skipped
Hanzo CI/CD / test-advisory (push) Skipped
Hanzo CI/CD / test-amd64 (push) Successful in 1m38s
Hanzo CI/CD / cicd (push) Successful in 8m2s
CI/CD / cicd (push) Successful in 9m46s

Co-authored-by: Hanzo Dev <[email protected]>
This commit is contained in:
2026-09-27 17:01:13 -07:00
co-authored by Hanzo Dev
parent 96f2140b4b
commit 4ac2da9c22
+8 -2
View File
@@ -4,8 +4,9 @@
# .hanzo/workflows/ci.yml (`make -k all` under texlive-full), which is the right
# home for a 219-paper, texlive-sized job.
#
# No deploy:. hanzoai/universe pins which tag is live; a build never deploys
# itself.
# papers.hanzo.ai serves a static export: the route in hanzoai/universe
# (static-sites.yaml, papers-static) reads s3://hanzo-sites/hanzo/papers, and
# site: below is what writes it, from main. The image is the build gate.
#
# No version: either. imgver reads the image's own context before the repo root,
# so site/package.json is where this version lives and a key here could only
@@ -21,3 +22,8 @@ images:
# which needs a context at the repository root, which is why the context is
# `.` and .dockerignore carries the weight instead.
platforms: [linux/amd64, linux/arm64]
site:
slug: papers
dir: site/out
build: cd site && npm ci && npm run build
on: [main]