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

Merged
DO
6d ago
+741-2

User description

This records the v0.1.8 cut as release/fixtures/cut.v0-1-8.json, in the same form as #737's cut.v0-1-7.json. The Factory Builder asked for it on 2026-11-11.

Model Lens inputs touched: none. The change is the fixture, tests/test_release.py and tools/mutants.py.

Size. 35,700 characters and 785 lines by git diff; about 41,200 as the Kernel counts a diff, with its lines numbered, against a budget of 60,000.

What GitHub answered

  • Release run 43110557016 (release.yml, success) cut factory/v0.1.8 at caa39652, the merge of "The CLI's install fetches bubblewrap by a source list of its own from a mirror the runners resolve, not the image's mirror list" (#748). It moved factory/v0-next there and recorded Deployment 7722549166, whose status is success. The fixture holds the run, its one job, and the job's log at the step.
  • Eval run 43107717326 (eval.yml, workflow_dispatch, success) ran on caa39652. It ended at 22:17:05Z, before the cut was asked at 22:17:50Z, and the eval workflow lists it as its only run on that commit.
  • Read after the cut (22:19Z):
    • factory/v0.1.8 and next both name caa39652.
    • factory/v0.1.7 still names 68efced8, where its cut left it.
    • next has nine Deployments, newest first: v0.1.8's down to v0.1.0's.
    • GitHub marked v0.1.7's inactive and kept its earlier success.

The reads went through the Maintainer's login and were trimmed to cut.v0-1-7.json's fields and headers, read for read, by lane e's builder. 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.7. removed says what was taken, word for word as v0.1.7's. gitleaks finds no leaks.

Checks it adds

  • tests/test_release.py::test_the_next_cut_moved_next_on: v0.1.8 joins its list, held to the cut's writes, the eval run ended before the cut and the one run on its commit, both tags, v0.1.7 where it was, all nine Deployments, and both statuses.
  • Nine mutants of the new fixture, each killed by that test, as for v0.1.7.

No record is needed: no rule changes.

Checks

CheckResult
make checksOK
tests.test_releaseOK, 29 tests
The nine new mutants9 of 9 killed
gitleaks on the fixtureNo leaks
ReaderHeadState
Carbon (gemini-4-carbon-high)ca0aa6b4A clean read, in two parts
Muse (Wonder Full)3df3ec8eA clean read
Astra (gpt-6-astra)3df3ec8eA clean read
Claude + securityca0aa6b4Nothing blocking. Every value re-read against GitHub matches; no credential left. One wording fix to the test's comment, in 3df3ec8e

🤖 Generated with Claude Code


CodeAnt-AI Description

Record and verify the v0.1.8 release cut

What Changed

  • Records the successful v0.1.8 release and the move of next to its commit
  • Confirms the evaluation passed before the cut and the new deployment succeeded
  • Verifies v0.1.7 remains at its original commit and its deployment is marked inactive

Impact

✅ v0.1.8 release recorded
✅ next points to v0.1.8
✅ v0.1.7 remains pinned to its original commit

💡 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.