v0.11.0 polish: the Debug Build message, the release badge on tags, the CI timings #56

2026-10-06T15:06:37Z

twisla commented

2026-10-06 15:06:37 +00:00

Three small things v0.11.0 showed.

The Debug Build message fits the screen. A Debug Build keeps its console: update it from your PC ran off the edge of the release page; it now reads Debug Build: update from the PC. Checked on the device (the release page's last line, with the device pretending to run an older Debug Build).
The release badge follows a tag. After v0.11.0 was published the README's badge still said v0.10.0, because CI only drew it on a push to main. Tag runs already run the tests and coverage; they now publish the badges too. (This workflow change is in this PR's own head, so the PR run uses it; whether a tag run publishes the badge is only seen at the next tag.)
The CI timings in docs/milestones/R1.md are the jobs' own measured durations: the first full run took 11.4 minutes, not 17 (that was waiting time).

456 host tests pass and both firmwares build locally.

🤖 Generated with Claude Code

https://claude.ai/code/session_01EhqxQ49eCju4CzKYNjZzwT

Three small things v0.11.0 showed. - **The Debug Build message fits the screen.** `A Debug Build keeps its console: update it from your PC` ran off the edge of the release page; it now reads `Debug Build: update from the PC`. Checked on the device (the release page's last line, with the device pretending to run an older Debug Build). - **The release badge follows a tag.** After v0.11.0 was published the README's badge still said v0.10.0, because CI only drew it on a push to `main`. Tag runs already run the tests and coverage; they now publish the badges too. (This workflow change is in this PR's own head, so the PR run uses it; whether a tag run publishes the badge is only seen at the next tag.) - **The CI timings in `docs/milestones/R1.md`** are the jobs' own measured durations: the first full run took 11.4 minutes, not 17 (that was waiting time). 456 host tests pass and both firmwares build locally. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01EhqxQ49eCju4CzKYNjZzwT

twisla added 3 commits 2026-10-06 15:06:37 +00:00

R1 plan: the CI timings, measured from the jobs' own start and end times 325e7755ad

The first full run took 11.4 minutes, not 17: that was the waiting time.
A pull request takes about 8.7, a release build alone 5.5, a push to main
1.1.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EhqxQ49eCju4CzKYNjZzwT

Updates: the Debug Build message fits on one line of the screen 148611ff4c

"A Debug Build keeps its console: update it from your PC" ran off the
edge of the release page. It now reads "Debug Build: update from the PC".

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EhqxQ49eCju4CzKYNjZzwT

CI: the release badge follows a tag, not only a push to main

CI / build (pull_request) Successful in 8m6s

Details

12006bdf94

After v0.11.0 was published the badge still said v0.10.0 until the next
push to main. Tag runs run the tests and coverage already; they now
publish the badges too.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EhqxQ49eCju4CzKYNjZzwT

twisla merged commit 4f0918ceae into main

2026-10-06 15:21:43 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: twisla/roro9stack#56