fix(ci): qualify first release hardening#91
Draft
f0rr0 wants to merge 1 commit into
Draft
Conversation
f0rr0
force-pushed
the
f0rr0/release-hardening-qualification
branch
from
July 17, 2026 13:57
b264512 to
50e15bb
Compare
f0rr0
force-pushed
the
f0rr0/release-hardening-qualification
branch
from
July 17, 2026 18:11
50e15bb to
e1b198d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Qualification-only transport for the first-release hardening tree. Do not merge this PR.
The transport commit is based on the current displaced
mainsolely so GitHub can exercise the complete PR matrix. Its tree is byte-identical to the signed introduction commit that will be used for the separately approved history repair.Exact identities
a70efaf647b5f62480aa43685bf8434fe3e5bfd307a9054faa03d5737dc0193f7a77ed4a71920c0550e15bb7364a48c04e0563484cd009df4e3d320606816d377f96ab8e53d3c6ec8732577cc4386f2ec5f95edcb442c8adb5e76585c1825519749da6e5Local proof
No history repair or publication is authorized by merging this PR. After exact-SHA hosted qualification succeeds, the protected-main repair remains a separate explicitly approved operation.