Repository navigation
ci: adopt staged policy Go 1.27.2 floor - #1066
Merged
Merged
Conversation
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.
Adopt the staged Go 1.27.2 floor for the isolated public-workflow policy analyzer. Restore the pinned module, checker, tests and wrapper, and rotate the three existing wrapper execution digests. This intentionally removes R4's budget-equivalence helper, fixture-reader plumbing and four associated tests now that the budget transition is adopted.
The reviewed head is
7248bad7c31fd6c4682f5b01474c5c3dda6ee7a2, based on accepted main76e5dd595e10908e90eae6a27ddbfcd72a5baf62, with treee4fc6c60a42844528c4c9968413b29e7a2bece4d. Exactly five files differ; all 3,527 nonowner files and modes, 38 staged pins, workflows, guard, harness and other trust maps are preserved. The failed4e442b1brun remains in history, and its original resolver failure cause remains unproved.Validation:
The official OSV differential reports no added findings and 21 policytool-only removals; all 351 surviving finding objects are unchanged. Known loading failures leave analysis UNKNOWN, with no clean or complete security claim under the existing scoped timing decision. The benchmark's unsupported-listing failure remains advisory. Protected integration and actual-main/snapshot acceptance are the next checkpoint.