-
-
Notifications
You must be signed in to change notification settings - Fork 0
fix(ci): pin third-party actions to full commit SHAs #86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win
🔎 Supported by static analysis
🏁 Script executed:
Repository: hyperpolymath/proven-servers
Length of output: 3677
🏁 Script executed:
Repository: hyperpolymath/proven-servers
Length of output: 17923
🌐 Web query:
official gh actions-lockfile documentation gh actions-lock update workflow pins actions.lock💡 Result:
<search_synthesis>
There are two distinct projects related to GitHub Actions lockfiles, both of which aim to solve the lack of native lockfile support in GitHub Actions by pinning dependencies to immutable commit SHAs [1][2][3]. 1. GitHub&
#39;s Officialgh-actions-lockExtension This is an official GitHub project that provides a CLI extension for the GitHub CLI (gh) [3]. - Purpose: It scans workflows in.github/workflows/, pins all resolvable actions to immutable commit SHAs, and maintains a lockfile at.github/workflows/actions.lock[3]. - Usage: Install viagh extension install github/gh-actions-lock[4]. Rungh actions-lockto generate or update the lockfile [3]. - Updating Pins: By default, it trusts existing pins in the lockfile [3]. To update (bump) pins to the current upstream commit, use the--relockflag:gh actions-lock --relock[3]. 2. Community Project:gh-actions-lockfile(by gjtorikian) This is a separate, popular community-maintained tool [1][5]. - Purpose: It generates and verifies lockfiles, supporting both a CLI and a GitHub Action for CI/CD integration [1][6]. - Usage: It can be used as a GitHub Action in your workflow to verify that dependencies match the lockfile [1]. - Updating Pins: When you update an action version in your workflow (e.g., from@v4to@v5), the verification job will fail, which can be configured to automatically trigger an update job to regenerate and commit the lockfile to your PR [6][5]. Key Differences -github/gh-actions-lockis the official GitHub-led effort to define the authoritative lockfile format and tooling [2][3]. It focuses on security by enforcing that locked commits are reachable from the repository's refs and blocking repository redirects [3][4]. -gjtorikian/gh-actions-lockfileis a mature community tool that provides robust CI/CD integration (e.g., automatic PR comments and verification steps) [1][6]. Both tools use the same general concept of pinning actions to SHAs to prevent "tag hijacking" and ensure consistent, secure workflow execution [1][3]. Note that these tools are distinct from Renovate's digest pinning, which is a separate mechanism for automated dependency updates [7].</search_synthesis>
<source_evidence>
Citations:
Regenerate the Actions lockfile for all affected workflows.
.github/workflows/actions.lockis generated bygh actions-lock, and the A2ML, K9, CICD-suite, and Rust toolchain entries are all recorded in that manifest. Run the comprehensive regeneration, such asgh actions-lock --relock, for the intended revisions. This updates the generated pins together; separate manual edits to each workflow call site are not required.🤖 Prompt for AI Agents