Skip to content

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

Merged
don-petry merged 2 commits into
mainfrom
claude/cut-v0-1-8
Nov 11, 2026
Merged

don-petry merged 2 commits into
mainfrom
claude/cut-v0-1-8

Conversation

@don-petry

@don-petry don-petry commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

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 caa3965, 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" (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 (#743) #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 caa3965. 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 caa3965.
    • factory/v0.1.7 still names 68efced, 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

Check Result
make checks OK
tests.test_release OK, 29 tests
The nine new mutants 9 of 9 killed
gitleaks on the fixture No leaks
Reader Head State
Carbon (gemini-4-carbon-high) ca0aa6b A clean read, in two parts
Muse (Wonder Full) 3df3ec8 A clean read
Astra (gpt-6-astra) 3df3ec8 A clean read
Claude + security ca0aa6b Nothing blocking. Every value re-read against GitHub matches; no credential left. One wording fix to the test's comment, in 3df3ec8

🤖 Generated with Claude Code

View guided diff Turn on auto-fix


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.

don-petry and others added 2 commits November 11, 2026 16:21
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@don-petry
don-petry requested a review from a team as a code owner November 11, 2026 22:55
@coderabbitai

coderabbitai Bot commented Nov 11, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

@codeant-ai

codeant-ai Bot commented Nov 11, 2026 •

Copy link
Copy Markdown

CodeAnt  CodeAnt Review Status

✅  Review completed

Status Commit Started (UTC) Finished (UTC)
✅  #751d1 Reviewed your PR 3df3ec8 Nov 11, 2026 · 22:55 22:58

@codeant-ai

codeant-ai Bot commented Nov 11, 2026

Copy link
Copy Markdown

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 11, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-11T22:57:27.404543Z 3df3ec8 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@codeant-ai codeant-ai Bot added the size:XL This PR changes 500-999 lines, ignoring generated files label Nov 11, 2026

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds a new release fixture cut.v0-1-8.json for version factory/v0.1.8 and integrates it into the test suite in tests/test_release.py as NINTH_CUT. I have no feedback to provide.

@sonarqubecloud

Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 3 files

View guided diff | Turn on auto-fix | Re-trigger cubic

@codeant-ai

codeant-ai Bot commented Nov 11, 2026

Copy link
Copy Markdown

CodeAnt  CodeAnt PR Risk

🟢  Low Risk

  • The PR appears safe to merge; no actionable issues were identified in the review.

Assessed commit: 3df3ec8e81b8

@combsmith-sf-pr-review combsmith-sf-pr-review Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No gating findings: the ninth cut's fixture, its test case and its mutants match the eighth's pattern.

@don-petry
don-petry added this pull request to the merge queue Nov 11, 2026
Merged via the queue into main with commit 1d23667 Nov 11, 2026
33 checks passed
@don-petry
don-petry deleted the claude/cut-v0-1-8 branch November 11, 2026 23:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:XL This PR changes 500-999 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants