Workflow dependency lockfiles
Web page · https://docs.github.com/en/actions/concepts/security/workflow-dependency-lockfiles
First seen by Oriel on .
AI summary
GitHub Actions workflow dependency lockfiles pin direct and transitive action dependencies to verified commits, improving reproducibility, reviewability, auditing, and protection against moved or compromised tags.
- The machine-generated .github/workflows/actions.lock file is created and updated using the gh actions-lock GitHub CLI extension, not edited manually.
- Each dependency records its original tag or branch, exact commit, and numeric repository identity, which GitHub verifies when workflows run.
- Locked commits must remain reachable from their recorded reference; fork-only or unreachable commits are rejected during workflow execution.
- Lockfiles do not cover reusable workflow calls, runner images, secrets, or inputs; reusable workflows require full-SHA references or lockfiles in their defining repositories.
- Compared with SHA pinning in workflow YAML, lockfiles support transitive dependencies, improve readability, record repository identity, and satisfy full-length SHA policies for onboarded workflows.
#github actions #supply chain security #dependency management #ci/cd
Generated by gpt-5.6-sol. Check the original for details.
Metric trends
Last 30 days · Up to 120 recorded samples per source and metric, with reposts kept separate · First and latest retained
Points
Score reported by the source.
- Lobsters: 5, latest observation ; +4 over observed period since
Comments
Comment count reported by the source.
- Lobsters: 0, latest observation ; 0 over observed period since
Aliases
| Source | External ID | URL |
|---|---|---|
| Lobsters | nft1s2 | https://docs.github.com/en/actions/concepts/security/workflow-dependency-lockfiles Read discussion |