Repository navigation
Conversation
This branch has not been deployed
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.
Checklist
No related issue: this is a CI-only change.
Adds GitHub's workflow dependency lockfile.
actions.lockrecords the commit behind every action the workflows use, so a moved tag can't change what runs. That includeschromium-headful-image.yamlandchromium-headless-image.yaml, wheredocker/login-action@v3receivesDOCKERHUB_TOKENanddocker/build-push-action@v6pushes theonkernel/chromium-*images, andserver-test.yaml, wherebrowser-actions/setup-chrome@v2runs in the job that holdsDOCKERHUB_TOKEN..github/workflows/actions.lock, generated with gh actions-lock and checked withgh actions-lock --verify(all 8 workflows valid).actions/checkout@v4.4.0anddocker/login-action@v3.7.0.oven-sh/setup-bunwas already pinned by SHA: it is now written asv2.2.0, the same commit, recorded in the lockfile. Onlyuses:lines change.kernel/security-workflows/...@main(breakglass.yml,semgrep.yml,vuln-remediation.yml). Job-level reusable workflow calls are not covered by a lockfile.Found by Plumber's analysis, reviewed and submitted by me.
Note
Low Risk
CI-only supply-chain hardening; no application runtime changes, only pinned GitHub Action versions and a generated lockfile.
Overview
Adds GitHub’s workflow dependency lockfile (
.github/workflows/actions.lock) and pins every in-repo workflow step to exact action release refs so CI runs fixed commits even if tags move.Across
chromium-headful-image.yaml,chromium-headless-image.yaml,chromium-launcher-test.yaml,live-view-test.yaml, andserver-test.yaml, floating tags likeactions/checkout@v4anddocker/login-action@v3become patch versions (e.g.v4.4.0,v3.7.0).oven-sh/setup-bunswitches from a SHA pin tov2.2.0, with that commit recorded in the lockfile.Reusable workflows (
breakglass.yml,semgrep.yml,vuln-remediation.yml) stay listed in the lockfile with no pinned actions because they delegate to external workflows.Reviewed by Cursor Bugbot for commit 9ff7188. Bugbot is set up for automated code reviews on this repo. Configure here.