tiennm99 b8e606f35c ci: verify the build before committing refreshed data ...

The CI failure on the merge commit was the one-time bootstrap ordering
problem: `go run . -build` ran before any data/metadata.json existed. The
nightly updater has since committed one, so the tree builds — but that
commit was pushed with GITHUB_TOKEN, which by design does not re-trigger
workflows, so CI never re-ran and main's status stayed red.

That exposes a standing gap rather than a one-off: every nightly refresh
commits the exact data the build consumes, and none of those commits run
CI. A refresh that broke the build would first be noticed by Cloudflare
at deploy time.

Run `go run . -build` in the update workflow between the fetch and the
commit, so data that does not build is never committed. Add
workflow_dispatch to CI so a bot-pushed commit can still be verified on
demand.

2026-09-16 22:30:58 +07:00

..

ci.yml

ci: verify the build before committing refreshed data

2026-09-16 22:30:58 +07:00

update.yml

ci: verify the build before committing refreshed data

2026-09-16 22:30:58 +07:00