Skip to content

Post-merge canary failure after #11627: unattended merging demoted #11658

Closed

Description

@github-actions

The post-merge check found a canary failure on main. The unattended merge path stays at
rung off while any demotion record is open. Fix main first, then close every open demotion record directly (not through a pull request's closing keyword); a new sighting of the same failure reopens its record.

To revert the merge, a human runs:

git revert b2f146273e14a4523b726cdf87414885914c573c

Activity

  1. added
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Oct 31, 2026
  2. kyle-sexton commented on Oct 31, 2026

    @kyle-sexton
    Member

    False positive, now acknowledged; closing directly as the body says.

    The canary attributed this record to #11627, but the finding in run 41225386123 names #11646 (5cce729c6) as removing 401 lines that #11548 (fd862a49b) landed. #11646 widened #11548's pr-verify chunk slots from 4 to 12. Every removed line is a 4-slot form whose 12-slot replacement lands in the same commit. Judge steps went from 15 to 39 and all 3 judge-spec steps remain, so no content was lost.

    #11669 records 5cce729c61018f709e9fa5216e639112e7f82daa in scripts/silent-revert-acknowledged.txt, with the file-by-file reading in its body. The canary skips that commit from now on, so this record has nothing left to report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions