The third cut and the move of next: release/fixtures/cut.v0-1-2.json

Merged
DO
7d ago
+675-13

This records the v0.1.2 cut as release/fixtures/cut.v0-1-2.json, in the same form as #690's cut.v0-1-1.json. The Factory Builder asked for it on 2026-11-10. It opens labelled factory:hands-off.

What GitHub answered

  • Release run 42741714653 (release.yml, success) cut factory/v0.1.2 at d960dc58, the merge of "The reader names the read GitHub did not answer, and the snapshot its part, by codes of their own (#688's dry run)" (#694). It moved factory/v0-next there, and recorded Deployment 7671661102, whose status is success. The fixture holds the run, its one job, and the job's log at the step.
  • Eval run 42739717534 (eval.yml, workflow_dispatch, success) ran on d960dc58. It ended at 02:16:08Z, before the cut was asked at 02:17Z, and the eval workflow lists it as its only run on that commit.
  • Read after the cut (02:21Z):
    • factory/v0.1.2 and next both name d960dc58.
    • factory/v0.1.1 still names 7ff090d7, where its cut left it.
    • next has three Deployments, newest first: v0.1.2's, v0.1.1's and v0.1.0's.
    • GitHub marked v0.1.1's inactive when the new one was made, and kept its earlier success.

The reads went through the Maintainer's login and were trimmed to cut.v0-1-1.json's fields and headers, read for read. tools/redact_trial.py redacted them outside the repo, and only the clean output was read. It took out the names of steps[1] and steps[6], the token's mint and its post step; this run has one step more than v0.1.1's, the upload of the step's own exchanges (decision 0176). Of the log's inputs, the token's line, which GitHub masked, and the exchanges' folder are left out, since tools/check_release.py keeps the four inputs a cut is asked by. removed says what was taken.

Checks it adds

  • tests/test_release.py::test_the_next_cut_moved_next_on now reads each cut after the first, through one helper, a_later_cut_moved_next_on. For v0.1.2 it holds:
    • the cut's writes;
    • the eval run (by id, workflow, event, conclusion and commit), ended before the cut, and the one run on its commit;
    • both tags at the cut commit, and v0.1.1 where it was;
    • all three Deployments in order, newest first, and both statuses.
  • Nine mutants of the new fixture, each killed by that test, as #690's are for v0.1.1: another eval workflow, run or commit; an eval that ended after the cut; another run listed on the commit; v0.1.1 moved; the newest Deployment not v0.1.2's; its status not success; v0.1.1's Deployment still reading only success.
  • release/AGENTS.md's cut row already names the test, and is unchanged.

No record is needed: no rule changes.

Checks

CheckResult
make checksOK
tests.test_releaseOK, 29 tests
Mutants of both later cuts' fixtures, run alone on an export18 of 18 killed
gitleaks on the fixtureNo leaks
Full make verifyNot run locally, by the Maintainer's standing change of 2026-11-09; CI's verify is the answer
ReviewerHeadUnread partsBlockingMajorMinorInfo
agy (Argon)81e3ec7none0000
muse81e3ec7none0000
astra81e3ec7none0000
claude-review81e3ec7none0000
claude-security81e3ec7none0000

šŸ¤– Generated with Claude Code