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>
A rabbit checks each workflow line
Tags and SHAs now align
Actions-lock leaves its mark
Permissions guide the scan in dark
CI hops onward, neat and bright
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 pull request aims to stabilize CI workflows by fixing YAML syntax and implementing dependency locking. However, current Codacy analysis indicates the changes are not up to standards.
A significant gap exists between the stated acceptance criteria and the implementation: while the PR intended to pin actions to specific versions/SHAs to support locking, the 'dawidd6/action-send-mail' action was pinned to a mutable version tag ('v3.12.0') instead of a 40-character commit SHA. This undermines the security goals of the PR.
Additionally, the permissions block in the secret scanning workflow is missing the 'security-events: write' scope, which is typically required for results to properly populate the GitHub Security dashboard. Fixing this is recommended to ensure the CI remains functional for security reporting.
About this PR
The specific invalid YAML syntax described (scalar permissions followed by indented mappings) is not explicitly visible in the provided diff hunks, making the 'unbreaking' part of the fix difficult to verify. Additionally, no automated linting was added to the repository to prevent future regressions regarding SPDX header placement or lockfile completeness.
Test suggestions
Verify that the SPDX-License-Identifier header is located on the first line of every workflow file.
Verify that all GitHub Actions and reusable workflows are pinned to specific versions or SHAs.
Verify that every workflow in the repository is covered by an entry in the actions.lock file.
Verify that the permissions block in every workflow is syntactically valid and includes 'actions: read' where required.
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Verify that the SPDX-License-Identifier header is located on the first line of every workflow file.
2. Verify that all GitHub Actions and reusable workflows are pinned to specific versions or SHAs.
3. Verify that every workflow in the repository is covered by an entry in the actions.lock file.
4. Verify that the permissions block in every workflow is syntactically valid and includes 'actions: read' where required.
The reason will be displayed to describe this comment to others. Learn more.
🔴 HIGH RISK
Pinning third-party actions to a full 40-character commit SHA ensures that the action code cannot be modified without a visible change to the workflow file. Version tags like 'v3.12.0' can be moved by the maintainer to point to different commits.
Try running the following prompt in your IDE agent:
Find the full commit SHA for the tag 'v3.12.0' of the 'dawidd6/action-send-mail' repository and replace the version tag with that SHA, appending the version number as a comment (e.g., uses: dawidd6/action-send-mail@ # v3.12.0).
The reason will be displayed to describe this comment to others. Learn more.
🟡 MEDIUM RISK
Suggestion: The workflow defines explicit permissions but omits security-events: write. Most secret scanning tools require this permission to report findings to the GitHub Security dashboard. Consider adding it to ensure results are properly integrated.
Suggested change
actions: read
security-events: write
actions: read
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