fix(ci): onboard workflows to dependency lock - #10
Merged
Conversation
|
|
hyperpolymath
force-pushed
the
agent/resolve-startup-failures
branch
from
August 18, 2026 15:00
64052f8 to
9f67fe0
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
1 participant
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.
GitHub rejected 27 post-policy workflows with the startup banner:
Workflow must use a lockfile. This onboards all 32 workflows through the authoritativegh actions-locktool, creates the generated lock, refreshes three moved branch refs, and replaces one unreachable historical ruby/setup-ruby SHA through its documented v1.210.0 ref.\n\nValidation: Actionlint workflow/YAML checks;gh actions-lock --verify-local --no-fix=> valid true, zero findings;git diff --check.\n\nDownstream remediation for metadatastician-governance#14.