The seventh cut and the move of next: release/fixtures/cut.v0-1-6.json
User description
This records the v0.1.6 cut as release/fixtures/cut.v0-1-6.json, in the same form as #723's cut.v0-1-5.json. The Factory Builder asked for it on 2026-11-10. It opens labelled factory:hands-off.
What GitHub answered
- Release run 42925869303 (
release.yml, success) cut factory/v0.1.6 at 48687f2a, the merge of "Config: no author Role is named until its manifest exists, so no fix Run is dispatched to a missing Role (#675, record 0189)" (#717). It movedfactory/v0-nextthere, and recorded Deployment 7697435186, whose status is success. The fixture holds the run, its one job, and the job's log at the step. - Eval run 42923463050 (
eval.yml,workflow_dispatch, success) ran on 48687f2a. It ended at 23:43:42Z, before the cut was asked at 23:44:48Z, and the eval workflow lists it as its only run on that commit. - Read after the cut (23:46Z):
- factory/v0.1.6 and
nextboth name 48687f2a. - factory/v0.1.5 still names 26d6c67e, where its cut left it.
nexthas seven Deployments, newest first: v0.1.6's, 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.5's
inactivewhen the new one was made, and kept its earlier success.
- factory/v0.1.6 and
The reads went through the Maintainer's login and were trimmed to cut.v0-1-5.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.5. 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_onreads each cut after the first; v0.1.6 joins its list. For v0.1.6 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.5 where it was;
- all seven Deployments in order, newest first, and both statuses.
- Nine mutants of the new fixture, each killed by that test, as for v0.1.5: another eval workflow, run or commit; an eval that ended after the cut; another run listed on the commit; v0.1.5 moved; the newest Deployment not v0.1.6's; its status not success; v0.1.5'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
| Check | Result |
|---|---|
make checks | OK |
tests.test_release | OK, 28 tests |
| Mutants of the cuts' fixtures, run alone on an export | 63 of 63 killed |
| gitleaks on the fixture | No leaks |
Full make verify | Not run locally, by the Maintainer's standing change of 2026-11-09; CI's verify is the answer |
| Reviewer | Head | Unread parts | Blocking | Major | Minor | Info |
|---|---|---|---|---|---|---|
| agy (Carbon) | 9ae90ba | none | 0 | 0 | 0 | 0 |
| muse | 9ae90ba | none | 0 | 0 | 0 | 0 |
| astra | 9ae90ba | none | 0 | 0 | 0 | 0 |
| claude-review | 9ae90ba | none | 0 | 0 | 0 | 0 |
| claude-security | 9ae90ba | none | 0 | 0 | 0 | 0 |
No reader found anything.
🤖 Generated with Claude Code
CodeAnt-AI Description
Record and verify the v0.1.6 release cut
What Changed
- Records the successful v0.1.6 release at the commit that passed evaluation, with
factory/v0-nextmoved to that commit. - Confirms v0.1.5 remains on its original commit and its deployment is marked inactive after v0.1.6 succeeds.
- Adds checks that catch incorrect release, evaluation, and deployment details in the record.
Impact
✅ Confirms v0.1.6 and next point to the evaluated commit
✅ Preserves the v0.1.5 release reference
✅ Detects inaccurate release-cut records
💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
@codeant-ai ask: Your question here
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
@codeant-ai ask: Can you suggest a safer alternative to storing this secret?
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
@codeant-ai: Your feedback here
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
@codeant-ai: Do not flag unused imports.
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
@codeant-ai: review
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.