You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Remediates GitHub Workflow Dependency Locking (public preview, no changelog entry), which rejects runs at startup_failure — zero jobs, no logs, nothing in REST or GraphQL. Full analysis: hyperpolymath/standards#657.
Proven on hyperpolymath/anamnesis: 6 of 6 workflows dead → 0 startup_failure, 13 running.
Five steps, in order — each blocks the next
1. Unbreak the workflow YAML. Any permissions: carrying a scalar with an indented mapping under it:
permissions: read-allactions: read # <- mapping under a scalar. Unparseable.
This reaches past the one file: gh actions-lock refuses to run when any workflow in the repo fails to parse, so the repo can never acquire a lockfile and can never self-heal.
2. Repin standards reusables off commits with no actions.lock. The rejection requires the callee to be covered at the pinned SHA — unsatisfiable at a pre-lockfile commit.
3. Generate the lockfile with gh actions-lock.
4. Hand-add the reusable-caller entries the tool omits, as '<path>': [].
⚠️ Measured across 218 repos: P(startup_failure | has lockfile) = 91.7% vs 15.8% without — because every workflow a lockfile omits is rejected. A partial lock is worse than none. Running gh actions-lock and stopping there is how this outage spread.
5. Restore SPDX-License-Identifier to line 1, which the tool displaces with its own banner and which the workflow-security linter greps via head -1.
Verified before this PR was opened
0 unparseable workflows · lockfile covers every workflow, no omissions · SPDX on line 1 in every file. The script refuses to push if any of the three fails.
Remediates GitHub Workflow Dependency Locking (public preview), which
rejects runs at startup_failure with zero jobs and no logs. See
hyperpolymath/standards#657.
Five steps, in order, because each blocks the next:
1. Unbroke any workflow whose `permissions:` carried a scalar with an
indented mapping under it - blind-permissions-insertion damage. This
matters beyond the one file: gh actions-lock refuses to run when ANY
workflow in the repo fails to parse, so the repo could never acquire a
lockfile and could never self-heal.
2. Repinned hyperpolymath/standards reusables off commits that have no
actions.lock. The rejection requires the CALLEE to be covered at the
pinned SHA, which is unsatisfiable at a pre-lockfile commit.
3. Generated the lockfile with gh actions-lock.
4. Hand-added the reusable-workflow caller entries the tool omits, as
'<path>': []. Measured across 218 repos: P(startup_failure | has
lockfile) = 91.7% vs 15.8% without, because every workflow a lockfile
OMITS is rejected. A PARTIAL lock is worse than none - running
gh actions-lock and stopping there is how this outage spread.
5. Restored SPDX-License-Identifier to line 1, which the tool displaces
with its own banner and which the workflow-security linter greps with
head -1.
Verified before push: 0 unparseable workflows, lockfile covers every
workflow with no omissions, SPDX on line 1 in every file.
Proven on hyperpolymath/anamnesis: 6 of 6 workflows dead -> 0
startup_failure, 13 running.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Reviewing files that changed from the base of the PR and between c75c6d9 and da86af1.
⛔ Files ignored due to path filters (1)
.github/workflows/actions.lock is excluded by !**/*.lock
📒 Files selected for processing (10)
.github/workflows/boj-build.yml
.github/workflows/codeql.yml
.github/workflows/docs.yml
.github/workflows/governance.yml
.github/workflows/instant-sync.yml
.github/workflows/mirror.yml
.github/workflows/pages.yml
.github/workflows/push-email-notify.yml
.github/workflows/scorecard.yml
.github/workflows/secret-scanner.yml
📝 Walkthrough
Summary by CodeRabbit
Chores
Updated automated workflow actions and reusable workflow references to newer maintained versions.
Standardised action version management across build, documentation, security, synchronisation, notification, mirroring and deployment workflows.
Updated GitHub Pages tooling and related automation components for improved maintenance and reliability.
Walkthrough
The workflows add gh actions-lock management comments and update action references. Standard actions use newer tags. Reusable workflow references use a newer commit. Workflow logic remains unchanged.
Changes
Workflow reference updates
Layer / File(s)
Summary
Standard action version updates .github/workflows/boj-build.yml, .github/workflows/codeql.yml, .github/workflows/docs.yml, .github/workflows/pages.yml
The workflows add management comments and update checkout, CodeQL, and Pages action references.
A rabbit checks the workflow trail
New action tags replace the stale
The lock-note sits above the flow
Secure references now show
Hop, hop, builds are ready to go
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
The PR aims to stabilize GitHub Actions workflows by fixing YAML syntax errors and implementing a comprehensive lockfile mechanism. While it successfully addresses the identified startup failures and ensures internal workflows are pinned to specified commits, the overall analysis is not up to standards. The review identified critical security concerns regarding the use of mutable tags for actions that handle sensitive credentials or trigger cross-repository events. Specifically, workflows for email notifications and repository dispatching should be pinned to immutable commit SHAs to prevent potential supply-chain attacks. Addressing these security practices is necessary to ensure the integrity of the CI/CD pipeline.
About this PR
The use of mutable version tags for GitHub Actions that handle sensitive credentials or tokens represents a security risk. Transitioning to immutable commit SHAs across all workflows is recommended to prevent potential supply-chain attacks where a tag could be redirected to malicious code.
Test suggestions
Verify SPDX-License-Identifier is preserved on line 1 in all modified workflows
Verify 'managed by gh actions-lock' banner is present on line 2
Update/Pin actions/checkout to v7.0.1 across all applicable workflows
Repin hyperpolymath/standards reusable workflows to current SHAs
The reason will be displayed to describe this comment to others. Learn more.
🔴 HIGH RISK
Pin the 'peter-evans/repository-dispatch' action to a full 40-character commit SHA. This ensures that the code being executed is exactly what was intended and has not been tampered with.
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
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.
![codacy-production[bot]](https://avatars.githubusercontent.com/in/56611?s=60&v=4){kind=small}
Remediates GitHub Workflow Dependency Locking (public preview, no changelog entry), which rejects runs at
startup_failure— zero jobs, no logs, nothing in REST or GraphQL. Full analysis:hyperpolymath/standards#657.Proven on
hyperpolymath/anamnesis: 6 of 6 workflows dead → 0startup_failure, 13 running.Five steps, in order — each blocks the next
1. Unbreak the workflow YAML. Any
permissions:carrying a scalar with an indented mapping under it:This reaches past the one file:
gh actions-lockrefuses to run when any workflow in the repo fails to parse, so the repo can never acquire a lockfile and can never self-heal.2. Repin
standardsreusables off commits with noactions.lock. The rejection requires the callee to be covered at the pinned SHA — unsatisfiable at a pre-lockfile commit.3. Generate the lockfile with
gh actions-lock.4. Hand-add the reusable-caller entries the tool omits, as
'<path>': [].P(startup_failure | has lockfile) = 91.7%vs15.8%without — because every workflow a lockfile omits is rejected. A partial lock is worse than none. Runninggh actions-lockand stopping there is how this outage spread.5. Restore
SPDX-License-Identifierto line 1, which the tool displaces with its own banner and which the workflow-security linter greps viahead -1.Verified before this PR was opened
0unparseable workflows · lockfile covers every workflow, no omissions · SPDX on line 1 in every file. The script refuses to push if any of the three fails.🤖 Generated with Claude Code