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

Merged
DO
7d ago
+667-2

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

What GitHub answered

  • Release run 42755427902 (release.yml, success) cut factory/v0.1.3 at c2a5795d, the merge of "A check's App another App's token is not shown reads as null, and is never a Lens's (#688's second dry run)" (#708). It moved factory/v0-next there, and recorded Deployment 7673508787, whose status is success. The fixture holds the run, its one job, and the job's log at the step.
  • Eval run 42753588971 (eval.yml, workflow_dispatch, success) ran on c2a5795d. It ended at 04:21:30Z, before the cut was asked at 04:22:13Z, and the eval workflow lists it as its only run on that commit.
  • Read after the cut (04:2xZ):
    • factory/v0.1.3 and next both name c2a5795d.
    • factory/v0.1.2 still names d960dc58, where its cut left it.
    • next has four Deployments, newest first: v0.1.3's, v0.1.2's, v0.1.1's and v0.1.0's.
    • GitHub marked v0.1.2'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-2.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, as for v0.1.2. 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 reads each cut after the first; v0.1.3 joins its list. For v0.1.3 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.2 where it was;
    • all four Deployments in order, newest first, and both statuses.
  • Nine mutants of the new fixture, each killed by that test, as for v0.1.2: another eval workflow, run or commit; an eval that ended after the cut; another run listed on the commit; v0.1.2 moved; the newest Deployment not v0.1.3's; its status not success; v0.1.2'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 the three later cuts' fixtures, run alone on an export36 of 36 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)38ed8aenone0000
muse38ed8aenone0000
astra38ed8aenone0000
claude-review38ed8aenone0000
claude-security38ed8aenone0000

šŸ¤– Generated with Claude Code