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

opened this in answer to

Check · Review · Land · Live — No review yet. Next: reviewer, no review yet.

Ready to land

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.

Notes · 4 files · +25 −2

look green — it answered, no tests were run, ready for a look deploy 7250cdf

Check passeddeploy 7250cdf

Website spec: 26 findings (report only)

Look

10 pages beside main · 0 new to this pull

/apps

main

at 59903fa ·

this pull

In the dark

main

at 59903fa ·

this pull

at 7250cdf ·

/docs

main

at 59903fa ·

this pull

In the dark

main

at 59903fa ·

this pull

at 7250cdf ·

/explore

main

at 59903fa ·

this pull

In the dark

main

at 59903fa ·

this pull

at 7250cdf ·

/looks/failed

main

at 59903fa ·

this pull

In the dark

main

at 59903fa ·

this pull

at 7250cdf ·

/looks/missing

main

at 59903fa ·

this pull

In the dark

main

at 59903fa ·

this pull

at 7250cdf ·

/nope/nothing

main

at 59903fa ·

this pull

In the dark

main

at 59903fa ·

this pull

at 7250cdf ·

/notes

main

at 59903fa ·

this pull

In the dark

main

at 59903fa ·

this pull

at 7250cdf ·

/releases

main

at 59903fa ·

this pull

In the dark

main

at 59903fa ·

this pull

at 7250cdf ·

/review

main

at 59903fa ·

this pull

In the dark

main

at 59903fa ·

this pull

at 7250cdf ·

/security

main

at 59903fa ·

this pull

In the dark

main

at 59903fa ·

this pull

at 7250cdf ·

opened this

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.md is new. It describes the daily 10:30 UTC tick, its sequence, the hold rule and the The 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 is systemctl --user disable --now forge-release-tick.timer.
  • The footing row for release-tick in src/system/footing.ts and the matching row in docs/OPERATING.md said "a host timer every 5 min". Both now say "a host timer daily at 10:30 UTC".
  • test/footing.test.ts has 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_quiet alarm. The alarm fires after 60 minutes without a heartbeat. A daily timer that does not report to /api/v1/release/heartbeat would 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.md still 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.

Closes #14257

commented

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.md is new. It describes the daily 10:30 UTC tick, its sequence, the hold rule and the The 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 is systemctl --user disable --now forge-release-tick.timer.
  • The footing row for release-tick in src/system/footing.ts and the matching row in docs/OPERATING.md said "a host timer every 5 min". Both now say "a host timer daily at 10:30 UTC".
  • test/footing.test.ts has 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_quiet alarm. The alarm fires after 60 minutes without a heartbeat. A daily timer that does not report to /api/v1/release/heartbeat would 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.md still 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.
Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs