release-day
rigger release-day [--week <WEEK>] [--json]The week as the outside sees it. The rule it reads against is the one the line set for its shopfront: a release goes out on a Friday, and a version ready on a Tuesday waits in the queue.
The reason is not tidiness. Two releases on one day read as a single burst to anyone watching; two in different weeks read as a rhythm. What is meant to be even is the trace, not the effort - the work goes in bursts and always will.
$ rigger release-day --week 2026-W372026-W37 — releases on 2026-09-11
Waiting for Friday: sample v0.3.0 · Third
Already out this week: 2026-09-08 early 1 sample v0.1.0 2026-09-09 early 1 sample v0.2.0 2026-09-11 Friday 1 widget v0.1.0
2 releases past the one release this week has room for2 releases went out before FridayWaiting for Friday
Section titled “Waiting for Friday”Versions aimed at this week whose tag has not been made yet. This is the queue proper: what the Friday is for.
Already out this week
Section titled “Already out this week”What the tags say has shipped, folded by day. Each line is one day: the date, whether it is the week’s Friday, how many releases it carried, and which projects they came from.
A project’s versions are named while they are few and spanned once they are not - v0.1.0..v0.12.0 (12). The fold is not cosmetic. A real week of this line holds ninety-four releases, and a line each would put the two numbers that answer the question below the fold, where nobody reading a terminal would find them.
The two numbers
Section titled “The two numbers”The last lines say which half of the rule is being broken, and they are counts rather than complaints - the record reports, and what to do about it is yours.
- past the one release this week has room for - the week carried more than one release, so the trace shows a burst rather than a beat.
- went out before Friday - the tag was made earlier in the week, so the release did not wait its turn.
A week that kept the rule shows neither line.
--json
Section titled “--json”The same facts as data, with early and over_the_slot as numbers, and shipped and queued as lists. week and week’s shipping field read the same versions, so the two screens cannot disagree about a week.
Related
Section titled “Related”week- the Monday brief, of which this is one section.calendar- several weeks at once, as a grid.version plan- what puts a version in the queue.sync- what reads the tags this counts.