Skip to content

The fourteenth cut and the move of next: release/fixtures/cut.v0-1-13.json - #864

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

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

Conversation

@don-petry

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

Copy link
Copy Markdown
Contributor

This records the v0.1.13 cut as release/fixtures/cut.v0-1-13.json, in the same form as cut.v0-1-12.json. The Factory Builder asked for it on 2026-11-13. It closes no issue and carries no record.

Model-Lens inputs touched: none. Protected paths touched: none. The change is the fixture and tools/mutants.py, and goes by the Factory's route.

Size. 47,312 characters and 839 lines by a local diff against main; 54,563 characters as the Kernel counts a diff, with its lines numbered, against a budget of 60,000.

The fixture adds no line to tests/test_release.py. Since "A cut's fixture reads a page of next's Deployments, held to its order, and every cut after factory/v0.1.11 must (#792)" (#813) the test reads every cut's fixture from release/fixtures/ in version order, and the helper every later cut is read by is unchanged here.

What GitHub answered

The reads went through the Maintainer's login and were trimmed to cut.v0-1-12.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.12. removed says what was taken, and says one thing more than v0.1.12's does: the Link header GitHub answers on the page's read, which the trim to the older fixture's headers drops (the security pass's finding; see below).

Checks it adds

  • tests/test_release.py::test_the_next_cut_moved_next_on now reads this fixture with the rest, and holds of v0.1.13 all that it holds of v0.1.12.
  • Forty-six mutants of the new fixture, each killed by that test. They are the thirteenth cut's forty-six, carried over value for value: each value of the old fixture changed for the one the new fixture holds at the same line. Three kinds were then set by hand, so that each breaks the rule its name gives and no other:
    • the nine rows that turn on a time take the new fixture's own times;
    • the five rows that change a run's or a Deployment's id to another take the new fixture's id and one more;
    • the two rows of the page's third and fourth Deployments are renamed, since those are now the twelfth cut's and the move forward's.
  • release/AGENTS.md's cut row already names the test, and is unchanged.

Checks

Check Result
make checks OK, at a911946
tests.test_release OK, 38 tests, at a911946
The forty-six new mutants, each applied by hand 46 of 46 killed, at a911946
Mutants of the cuts' fixtures and of the rollback's, run alone on an export 238 of 238 killed, at 4ad0b4a
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

Since 4ad0b4a one sentence of the fixture's removed changed, which no mutant's text holds, and the branch was rebased on main.

Reviewer Head Unread parts Blocking Major Minor Info
agy (Carbon) 4ad0b4a not run (quota), owed – – – –
muse 4ad0b4a not run (the plan's usage limit), owed – – – –
claude-review 4ad0b4a none 0 0 0 1
claude-security 4ad0b4a none 0 0 0 2
astra 4ad0b4a none 0 0 0 0
Kimi e4d4c51 none 0 1 0 0

Kimi: 1 finding, 1 taken. Both Claude readers asked GitHub again for the reads they could, and each kept field agreed; each applied all forty-six mutants one at a time and found each killed at the assertion its name gives.

Finding What Disposition
Kimi #1 (major) The mutant "the eval workflow lists the fourteenth cut's eval run as ended after the cut" kept the thirteenth cut's time, which is before this cut: it was killed, but not for the reason it names fixed in 4ad0b4a: the new fixture's time, moved past the cut. The five ids carried as the old fixture's number and one were set to the new fixture's in the same pass
claude-review #1, claude-security #1 (info) Five fields of a cut's fixture are read by no test, in v0.1.12's fixture as in this one: the release run's own status and attempt, the job's name, the environment of the cut's Deployment's status, and the times of the statuses under the Deployment next moved off not here: it is the shared helper's, and a change of its own. Filed as "A cut's fixture has five fields no test reads, and drops the Link header of the read of next's Deployments" (#863)
claude-security #2 (info) The read of next's Deployments drops GitHub's Link header, one a fixture keeps, and removed did not say so. Carried over from v0.1.12's fixture and the rollback's this fixture's removed now says so. Whether a cut's fixture keeps and holds the header is in #863

🤖 Generated with Claude Code

View guided diff Turn on auto-fix

….json

Release run 43494364478 cut factory/v0.1.13 at 4e58ba4, the commit
eval run 43491470154 had passed, and moved next there with Deployment
7774706592. The fixture holds the same eleven reads as v0.1.12's, with
next's Deployments as a page of four (issue 792).

tests/test_release.py reads each cut's fixture from release/fixtures/,
so the test takes no line. Forty-six mutants of the fixture, the
thirteenth cut's carried over value for value, each killed by
test_the_next_cut_moved_next_on.

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 13, 2026 20:10
@coderabbitai

coderabbitai Bot commented Nov 13, 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 13, 2026 •

Copy link
Copy Markdown

CodeAnt  CodeAnt Review Status

✅  Review completed

Status Commit Started (UTC) Finished (UTC)
✅  #ef83e Reviewed your PR a911946 Nov 13, 2026 · 20:10 20:14

@codeant-ai

codeant-ai Bot commented Nov 13, 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 13, 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-13T20:13:17.901758Z a911946 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.

@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 release/fixtures/cut.v0-1-13.json containing detailed mock API responses and execution logs for a release cut operation. 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 2 files

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

@codeant-ai

codeant-ai Bot commented Nov 13, 2026

Copy link
Copy Markdown

CodeAnt  CodeAnt Nitpicks

1 code suggestion

1. This entry says the deployment response kept its pagination Link header, but that response has no Link key, making the fixture’s preservation record false.

Comment mismatch · release/fixtures/cut.v0-1-13.json:629

@codeant-ai

codeant-ai Bot commented Nov 13, 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: a911946b67d2

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants