Repository navigation
ci: promote realized Go policy authority floor - #1071
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.
Promotes the already realized Go 1.27.2 policy authority bundle so it becomes the sole active bundle and frees the staged slot. Task24 was accepted on actual main
49c550c4bf63f40a731cddcd9a4f00a48005c4a2; all 38 staged files match their recorded hashes before promotion.The only changed file is
.github/public-workflow-authority.json. Every source file, executable mode, workflow and E/C/A/P trust map remains exact. This is Task25 / SF4, followed separately by Task34’s CI-map promotion.Validation: the actual trusted-main wrapper accepts the candidate and scans all 11 workflows through the normal path without adoption guard, fallback or bootstrap; six uncached authority/trust lifecycle and rollback parents pass; the full unchanged fixture harness passes and restores production input. Its two internal package checks are honestly cached. Two independent scope-first/all-15 source reviews returned SHIP-IT with zero findings before publication. Exact-head hosted native/security/quality/protection gates and owning reviews remain required before integration; actual-main and automatic snapshot provenance plus final reviews govern acceptance.
Existing OSV incomplete analysis remains UNKNOWN, AnalysisComplete=false and SecurityClean=false under the already named Task25 timing boundary through separate source1022. No new finding or required-check waiver. Benchmark status remains advisory. Task35 is conditional/unperformed/open; whole-plan completion, fixed released Linux CLI, Compute runtime/customer acceptance and deployment are not claimed.