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 4ccec23 and ad88faa.
⛔ Files ignored due to path filters (1)
.github/workflows/actions.lock is excluded by !**/*.lock
📒 Files selected for processing (12)
.github/workflows/boj-build.yml
.github/workflows/casket-pages.yml
.github/workflows/codeql.yml
.github/workflows/dogfood-gate.yml
.github/workflows/governance.yml
.github/workflows/hypatia-scan.yml
.github/workflows/mirror.yml
.github/workflows/placement-guard.yml
.github/workflows/push-email-notify.yml
.github/workflows/scorecard.yml
.github/workflows/secret-scanner.yml
.github/workflows/verify-tlaplus.yml
📝 Walkthrough
Summary by CodeRabbit
Chores
Updated workflow configuration comments and permissions.
Refreshed pinned workflow action versions for security and maintenance.
Updated the email notification action version.
No changes to application functionality or user-facing behaviour.
Walkthrough
The pull request updates GitHub Actions workflow comments, permissions, reusable workflow commit pins, and the mail-sending action version. It does not change workflow job logic.
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
Codacy results indicate that this pull request is not up to standards. While the PR successfully resolves YAML syntax issues and restores necessary license headers, the 'actions.lock' file mentioned in the PR title and acceptance criteria is missing from the diff. This prevents verification of the primary goal: a complete and manually-augmented lockfile for all actions. Additionally, the workflow for email notifications uses a mutable version tag instead of a commit SHA, which introduces security risks and is inconsistent with the PR's objective of immutable pinning. Finally, a tool-related artifact has introduced duplicate header comments across all modified files.
About this PR
The 'actions.lock' file is missing from this PR. Since a complete lockfile is a primary focus of this change (including manual additions for reusable callers), please ensure it is included so it can be verified.
Redundant management headers have been introduced across all workflows. A duplicate line ('# This workflow is managed by gh actions-lock.') appears at line 3 in every file and should be removed.
Test suggestions
All modified workflows have valid YAML syntax and parse successfully
The actions.lock file contains exhaustive coverage of all workflows including manual additions
SPDX-License-Identifier is positioned at line 1 of every workflow file
Reusable workflow references are updated to specific pinned SHAs
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. The actions.lock file contains exhaustive coverage of all workflows including manual additions
The reason will be displayed to describe this comment to others. Learn more.
🔴 HIGH RISK
This third-party action is pinned to a mutable version tag. To ensure supply-chain security and immutability, it should be pinned to a full-length commit SHA. This change is also necessary to maintain consistency with the PR's goal of implementing a comprehensive locking mechanism via 'actions.lock'.
The reason will be displayed to describe this comment to others. Learn more.
⚪ LOW RISK
Nitpick: Duplicate header comment. This line is identical to line 2 and should be removed to keep the workflow header clean. This issue appears consistently across all modified workflow files.
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