Public: anyone can read this; the crew can change it.
The forge releases itself from its own host, daily at 10:30 UTC, with no laptop involved #14268
Check · Review · Land · Live — No review yet.
The repo's records now say what the host job does. The job itself, /srv/forge/release-tick/tick.sh on the host, is not in this repository, and I did not touch or test it. Footing and doc tests pass and tsc is clean.
look green — it answered, no tests were run, ready for a look deploy 7250cdf
Check passeddeploy 7250cdf
Website spec: 26 findings (report only)
- /board http://127.0.0.1:40045/board answered 303 — https://specification.website/
- /notes http://127.0.0.1:40045/notes answered 303 — https://specification.website/
- /review http://127.0.0.1:40045/review answered 303 — https://specification.website/
- /releases http://127.0.0.1:40045/releases answered 303 — https://specification.website/
- /system http://127.0.0.1:40045/system answered 303 — https://specification.website/
- /admin/limits http://127.0.0.1:40045/admin/limits answered 404 — https://specification.website/
- /maintenance http://127.0.0.1:40045/maintenance answered 303 — https://specification.website/
- /talk http://127.0.0.1:40045/talk answered 303 — https://specification.website/
- /flow http://127.0.0.1:40045/flow answered 303 — https://specification.website/
- /resilience http://127.0.0.1:40045/resilience answered 303 — https://specification.website/
- /boards?help http://127.0.0.1:40045/boards?help answered 303 — https://specification.website/
- /settings/crew http://127.0.0.1:40045/settings/crew answered 303 — https://specification.website/
- /settings/crew?help http://127.0.0.1:40045/settings/crew?help answered 303 — https://specification.website/
- /settings/security/controls http://127.0.0.1:40045/settings/security/controls answered 303 — https://specification.website/
- /settings/grants http://127.0.0.1:40045/settings/grants answered 303 — https://specification.website/
- /preview-admin/sample expected exactly one <h1>, found 2 — headings
- /preview-admin/sample/drop http://127.0.0.1:40045/preview-admin/sample/drop answered 303 — https://specification.website/
- /preview-admin/sample/data-move http://127.0.0.1:40045/preview-admin/sample/data-move answered 303 — https://specification.website/
- /preview-admin/sample/cut-over http://127.0.0.1:40045/preview-admin/sample/cut-over answered 303 — https://specification.website/
- /preview-admin/sample/next?pick expected exactly one <h1>, found 2 — headings
- /preview-admin/sample/bets expected exactly one <h1>, found 2 — headings
- /preview-admin/sample/waves expected exactly one <h1>, found 2 — headings
- /preview-admin/sample/space the first focusable element is not a skip link (an in-page #target link) — skip-link
- /looks/missing http://127.0.0.1:40045/looks/missing answered 404 — https://specification.website/
- /looks/failed http://127.0.0.1:40045/looks/failed answered 500 — https://specification.website/
- /nope/nothing http://127.0.0.1:40045/nope/nothing answered 404 — https://specification.website/
The repo's records now say what the host job does. The job itself, /srv/forge/release-tick/tick.sh on the host, is not in this repository, and I did not touch or test it. Footing and doc tests pass and tsc is clean. I did not run the full suite; the forge's check does that on push.
What changed
docs/features/nightly-release.mdis new. It describes the daily 10:30 UTC tick, its sequence, the hold rule and theThe nightly release was held: …issue. It also says what was proven on 2026-11-16 (fetch, comparison, gate) and what has not yet run unattended (tag, build, rig, promote). The stop command issystemctl --user disable --now forge-release-tick.timer.- The footing row for
release-tickinsrc/system/footing.tsand the matching row indocs/OPERATING.mdsaid "a host timer every 5 min". Both now say "a host timer daily at 10:30 UTC". test/footing.test.tshas a new test that fails if the old wording comes back.
What I left out
- I did not change the release keeper, the heartbeat or the
release_quietalarm. The alarm fires after 60 minutes without a heartbeat. A daily timer that does not report to/api/v1/release/heartbeatwould trip it every day. Whether the host script reports a heartbeat is unknown from here, so I left that as a question. docs/SECURITY-RUNBOOK.mdstill says the droplet's release timer honours/var/tmp/forge-release/release-hold. I could not tell whether the new script does, so I did not edit it.- The footing row still lists the machine as
pg-grand. The issue only says "the host". - The gate asked for a "Direction:" line on the second commit, and I wrote one (the pull adds a feature doc but no pipeline change). Its wording is a stand-in; edit it if a reviewer wants a better reason.
To try it
- Run
bun test test/footing.test.ts test/platform-doc.test.ts. - Read
docs/features/nightly-release.md.
The repo's records now say what the host job does. The job itself,
/srv/forge/release-tick/tick.shon the host, is not in this repository, and I did not touch or test it. Footing and doc tests pass andtscis clean. I did not run the full suite; the forge's check does that on push.What changed
docs/features/nightly-release.mdis new. It describes the daily 10:30 UTC tick, its sequence, the hold rule and theThe nightly release was held: …issue. It also says what was proven on 2026-11-16 (fetch, comparison, gate) and what has not yet run unattended (tag, build, rig, promote). The stop command issystemctl --user disable --now forge-release-tick.timer.release-tickinsrc/system/footing.tsand the matching row indocs/OPERATING.mdsaid "a host timer every 5 min". Both now say "a host timer daily at 10:30 UTC".test/footing.test.tshas a new test that fails if the old wording comes back.What I left out
release_quietalarm. The alarm fires after 60 minutes without a heartbeat. A daily timer that does not report to/api/v1/release/heartbeatwould trip it every day. Whether the host script reports a heartbeat is unknown from here, so I left that as a question.docs/SECURITY-RUNBOOK.mdstill says the droplet's release timer honours/var/tmp/forge-release/release-hold. I could not tell whether the new script does, so I did not edit it.pg-grand. The issue only says "the host".To try it
bun test test/footing.test.ts test/platform-doc.test.ts.docs/features/nightly-release.md.Closes #14257