ci: lock workflow dependencies with GitHub's actions.lock
CO
3d ago+90+90+01234567890123456789-20-20-01234567890123456789
Adds GitHub's workflow dependency lockfile. actions.lock records the commit behind every action the workflows use, so a moved tag can't change what runs. That includes release.yml, where KSXGitHub/github-actions-deploy-aur@v4.1.2 receives AUR_SSH_PRIVATE_KEY, goreleaser/goreleaser-action@v6 runs with GORELEASER_GITHUB_TOKEN, and aws-actions/configure-aws-credentials@v4 receives the AWS keys that push the CLI image.
- Added
.github/workflows/actions.lock, generated with gh actions-lock and checked withgh actions-lock --verify(all 4 workflows valid). - Action refs narrowed to exact releases, for example
actions/checkout@v5.1.0andgoreleaser/goreleaser-action@v6.4.0. Onlyuses:lines change. - Two things stay outside the lockfile:
goreleaser-actionruns withversion: latest, so the goreleaser binary is downloaded at its latest version on every release (an explicit version would close it), andgithub-actions-deploy-aurbuilds its container from a Dockerfile, whose base image a lockfile can't pin.
Found by Plumber's analysis, reviewed and submitted by me.