Skip to content

The eighth cut and the move of next: release/fixtures/cut.v0-1-7.json - #737

Merged
don-petry merged 1 commit into
mainfrom
claude/cut-v0-1-7-fixture
Nov 11, 2026
Merged

don-petry merged 1 commit into
mainfrom
claude/cut-v0-1-7-fixture

Conversation

@don-petry

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

Copy link
Copy Markdown
Contributor

User description

This records the v0.1.7 cut as release/fixtures/cut.v0-1-7.json, in the same form as #727's cut.v0-1-6.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,256 characters and 772 lines by git diff; 41,045 characters as the Kernel counts a diff, with its lines numbered, against a budget of 60,000.

What GitHub answered

The reads went through the Maintainer's login and were trimmed to cut.v0-1-6.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.6. 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.7 joins its list. For v0.1.7 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.6 where it was;
    • all eight Deployments in order, newest first, and both statuses.
  • Nine mutants of the new fixture, each killed by that test, as for v0.1.6: another eval workflow, run or commit; an eval that ended after the cut; another run listed on the commit; v0.1.6 moved; the newest Deployment not v0.1.7's; its status not success; v0.1.6'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, 29 tests
Mutants of the cuts' fixtures, run alone on an export 72 of 72 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) 99be1e6 none 0 0 0 0
muse 99be1e6 none 0 0 0 0
astra 99be1e6 none 0 0 0 0
claude-review 99be1e6 none 0 0 0 0
claude-security 99be1e6 none 0 0 0 0

No reader found anything. Carbon read it in two parts.

🤖 Generated with Claude Code

View guided diff Turn on auto-fix


CodeAnt-AI Description

Record and verify the v0.1.7 release cut

What Changed

  • Adds evidence that v0.1.7 was cut successfully from the evaluated commit and factory/v0-next moved to it, while v0.1.6 stayed on its previous commit.
  • Extends release checks to validate the new cut, its evaluation and deployment results, and earlier release references.

Impact

✅ Verifiable v0.1.7 release record
✅ Catches incorrect next-tag moves
✅ Preserves v0.1.6 release history

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

Release run 43026745268 cut factory/v0.1.7 at 68efced, #731's merge, on eval run 43024260112. The same reads as
cut.v0-1-6.json's, trimmed and redacted the same way; test_the_next_cut_moved_next_on reads it, and nine mutants of the
new fixture are killed by it.

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 13:24
@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)
✅  #ec3e4 Reviewed your PR 99be1e6 Nov 11, 2026 · 13:24 13:28

@chatgpt-codex-connector

Copy link
Copy Markdown
Codex Review Summary: ❌ Failed

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

Review Status Commit Review trigger
📝 Code Review ❌ Failed 2026-11-11T13:24:51.829913Z
We couldn’t complete this review. Comment @codex review to try again.
99be1e6 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 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

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@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 file "cut.v0-1-7.json" for version "factory/v0.1.7" and integrates it into the test suite in "tests/test_release.py" by defining "EIGHTH_CUT" and adding it to the parameterized test cases in "test_the_next_cut_moved_next_on". I have no feedback to provide as there are no review comments.

@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: 99be1e6a56d8

@don-petry
don-petry added this pull request to the merge queue Nov 11, 2026
Merged via the queue into main with commit 05177d5 Nov 11, 2026
32 checks passed
@don-petry
don-petry deleted the claude/cut-v0-1-7-fixture branch November 11, 2026 13:58
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