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

Merged
DO
7d ago
+694-2

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

What GitHub answered

  • Release run 42885151917 (release.yml, success) cut factory/v0.1.5 at 26d6c67e, the merge of "The approving act finds its Decision by the run-name's Intent, and its token may read a compare of two commits (#688's fourth dry run)" (#720). It moved factory/v0-next there, and recorded Deployment 7692024082, whose status is success. The fixture holds the run, its one job, and the job's log at the step.
  • Eval run 42882105104 (eval.yml, workflow_dispatch, success) ran on 26d6c67e. It ended at 19:23:47Z, before the cut was asked at 19:25:40Z, and the eval workflow lists it as its only run on that commit.
  • Read after the cut (19:29Z):
    • factory/v0.1.5 and next both name 26d6c67e.
    • factory/v0.1.4 still names c1edc4a4, where its cut left it.
    • next has six Deployments, newest first: v0.1.5's, v0.1.4's, v0.1.3's, v0.1.2's, v0.1.1's and v0.1.0's.
    • GitHub marked v0.1.4'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-4.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.4. 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.5 joins its list. For v0.1.5 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.4 where it was;
    • all six Deployments in order, newest first, and both statuses.
  • Nine mutants of the new fixture, each killed by that test, as for v0.1.4: another eval workflow, run or commit; an eval that ended after the cut; another run listed on the commit; v0.1.4 moved; the newest Deployment not v0.1.5's; its status not success; v0.1.4'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, 28 tests
Mutants of the cuts' fixtures, run alone on an export54 of 54 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 (Carbon)9d92f23none0000
muse9d92f23none0000
astra9d92f23none0000
claude-review9d92f23none0000
claude-security9d92f23none0002
FindingWhatDisposition
claude-security@9d92f23 #1 (info)Nothing holds the release run's head_branch or head_sha: a hand mutant of either survivesnot fixed here: the same holds for the cuts v0.1.1 to v0.1.4, and it is the shared helper's, a_later_cut_moved_next_on, not this fixture's
claude-security@9d92f23 #2 (info)The helper does not hold the reads' dates to be after the run ended, and hand mutants of the tag's object.type, the eval's run_attempt and its status survivenot fixed here, for the same reason

šŸ¤– Generated with Claude Code