Skip to content

The sixth cut and the move of next: release/fixtures/cut.v0-1-5.json - #723

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

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

Conversation

@don-petry

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

Copy link
Copy Markdown
Contributor

This records the v0.1.5 cut as release/fixtures/cut.v0-1-5.json, in the same form as #718's cut.v0-1-4.json. The Factory Builder asked for it on 2026-11-10. It opens labelled factory:hands-off.

What GitHub answered

The reads went through the Maintainer's login and were trimmed to cut.v0-1-4.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.4. 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.5 joins its list. For v0.1.5 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.4 where it was;
    • all six Deployments in order, newest first, and both statuses.
  • Nine mutants of the new fixture, each killed by that test, as for v0.1.4: another eval workflow, run or commit; an eval that ended after the cut; another run listed on the commit; v0.1.4 moved; the newest Deployment not v0.1.5's; its status not success; v0.1.4'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 54 of 54 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) 9d92f23 none 0 0 0 0
muse 9d92f23 none 0 0 0 0
astra 9d92f23 none 0 0 0 0
claude-review 9d92f23 none 0 0 0 0
claude-security 9d92f23 none 0 0 0 2
Finding What Disposition
claude-security@9d92f23 #1 (info) Nothing holds the release run's head_branch or head_sha: a hand mutant of either survives not fixed here: the same holds for the cuts v0.1.1 to v0.1.4, and it is the shared helper's, a_later_cut_moved_next_on, not this fixture's
claude-security@9d92f23 #2 (info) The helper does not hold the reads' dates to be after the run ended, and hand mutants of the tag's object.type, the eval's run_attempt and its status survive not fixed here, for the same reason

🤖 Generated with Claude Code

View guided diff Turn on auto-fix

Release run 42885151917 cut factory/v0.1.5 at 26d6c67, #720's merge, on eval run 42882105104. The same reads as
cut.v0-1-4.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 10, 2026 20:50
@don-petry don-petry added the factory:hands-off A person's mark: the Factory writes nothing on this pull request (kernel/terms.py LABEL_HANDS_OFF) label Nov 10, 2026
@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-10T20:50:10.639634Z
We couldn’t complete this review. Comment @codex review to try again.
9d92f23 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.

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

@coderabbitai

coderabbitai Bot commented Nov 10, 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

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@sonarqubecloud

Copy link
Copy Markdown

@don-petry
don-petry added this pull request to the merge queue Nov 10, 2026
Merged via the queue into main with commit 16ac8a6 Nov 10, 2026
30 checks passed
@don-petry
don-petry deleted the claude/cut-v0-1-5-fixture branch November 10, 2026 21:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

factory:hands-off A person's mark: the Factory writes nothing on this pull request (kernel/terms.py LABEL_HANDS_OFF)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant