You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 4b84d6b
Browse filesBrowse the repository at this point in the historyBrowse files
Update toast: changelog-forward design, and a restart that waits for you (#55)
The update toast led with a 12-char SHA, called the build "staged", and never
said what changed — the only interesting question on a fork you maintain
yourself. Its failure state printed a log path as unclickable text, and "Later"
duplicated the corner dismiss.
The toast now leads with the change count, puts the commit subjects behind a
"What changed" disclosure, pins the build age top-right linking to the workflow
run, and replaces "Later" with "Restart when idle".
Wired end to end: CI computes the changelog, the manifest carries it, and the
app renders it. The relay needed no deploy — it parses buildNumber for ordering
and treats the rest as opaque.
Decisions that carry risk:
The changelog is anchored on the previous RELEASE TAG, not branch ancestry. The
sync playbook force-pushes main, so a released commit may not be an ancestor of
it. Tags survive the rewrite, and `git log A..B` stays correct when A is not an
ancestor. Capped at 20.
Idleness reads latestTurn.state, not session.status — #38 records that
session.status deadlocks on synthetic turns, and a stuck status here means an
armed restart that never fires. Archived and settled threads are excluded; scope
is the primary environment only, since remote threads survive the restart.
An armed restart has a two-hour ceiling and stands DOWN on expiry. It does not
restart anyway (that kills the work the arm protected) and does not wait in
silence (#41's dark app with extra steps).
Silent-failure tripwires: RUN_ID is rejected when it equals RUN_NUMBER (they are
different numbers and the counter yields a 404); empty changelogs are omitted
rather than emitted; every new field is optional so an older manifest still
decodes, because a required one would fail the decode and silently withhold a
real update.
Commit subjects are attacker-influenced, so the GITHUB_OUTPUT heredoc uses a
random delimiter — with a fixed one a subject equal to that literal would close
it early and write arbitrary job outputs that this workflow uses to publish a
release.
No new upstream seam: ui/toast.tsx stays untouched.
Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
0 commit comments