Repository navigation
Lock workflow action dependencies with actions.lock - #26
Merged
Merged
Conversation
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
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.
Adds GitHub's workflow dependency lockfile.
.github/workflows/actions.lockrecords the commit behind every action the workflows use, so a moved tag on a third-party action can't change what runs in CI. That includespublish-npm.yml, which publishes the package, and the release and promotion workflows that useactions/create-github-app-token..github/workflows/actions.lockwas generated with gh actions-lock, not edited by hand.gh actions-lock --verifypasses (8 workflows valid).actions/checkout@v6.0.2andactions/create-github-app-token@v1.12.0, with the commit recorded in the lockfile. The commits are unchanged.pnpm/action-setupinrelease-please.ymlwas pinned to the SHA of the annotatedv4tag object; it is nowv4.3.0, which is the commit that tag points to and the versionci.ymlalready used.uses:lines change.kernel/security-workflows/...@main(semgrep.yml,vuln-remediation.yml). A lockfile does not cover reusable workflows.Stainless-generated workflows. Most workflow files here are maintained by the Stainless SDK generator, which has rewritten
uses:lines before (for example, "ci: pin GitHub Actions to commit SHAs"). If a later codegen run changes an action ref, it has to be re-locked withgh actions-lock, otherwise the workflow will fail the lockfile check. These edits may also show up as custom code in the generator and could conflict on a future workflow template change.