Repository navigation
ci(actions-lock): bring actions.lock back in line with the workflows - #139
Conversation
The lock had drifted from the workflow files. GitHub refuses to start a workflow whose uses: set doesn't match its lock entries, and rejects a lock entry that records its own SHA as ref. - `casket-pages.yml`: `haskell-actions/setup@v2.12.0` → `haskell-actions/setup@v2.12.1` (the workflow already uses `v2.12.1`) - `push-email-notify.yml`: `hyperpolymath/smtp-notify-action@v0.3.0` → `hyperpolymath/smtp-notify-action@v0.5.0` (the workflow already uses `v0.5.0`) - `release.yml`: `actions/download-artifact@v8.0.1` → `actions/download-artifact@v8.0.2` (the workflow already uses `v8.0.2`) - `release.yml`: `actions/upload-artifact@v7.0.1` → `actions/upload-artifact@v7.0.2` (the workflow already uses `v7.0.2`) - new record `actions/download-artifact@v8.0.2` (ref `v8.0.2`, commit `9000827ccba6…`) - new record `actions/upload-artifact@v7.0.2` (ref `v7.0.2`, commit `cf430e030ddb…`) - new record `haskell-actions/setup@v2.12.1` (ref `v2.12.1`, commit `0f8e8c99d88a…`) - new record `hyperpolymath/smtp-notify-action@v0.5.0` (ref `v0.5.0`, commit `c1c9fa07992a…`) - remove the record `actions/download-artifact@v8.0.1`, which no entry references any more - remove the record `actions/upload-artifact@v7.0.1`, which no entry references any more - remove the record `haskell-actions/setup@v2.12.0`, which no entry references any more - remove the record `hyperpolymath/smtp-notify-action@v0.3.0`, which no entry references any more Each new record's commit was checked against the upstream tag with git ls-remote. No commit an existing entry pins was changed. Standards reusable pins are left as they are. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0132Cdz3iwk2QGKv2sUhhsye
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters: 1
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including
|
|
CI note: the red checks on this PR don't come from this change. The PR edits only
No fix exists yet for any of these, so I haven't ported one. Generated by Claude Code |
|
Add Carrot credits or activate Agent usage billing to use Autofix |
Summary
actions.lockhad drifted from the workflow files. Dependabot bumped actions in the YAML without regenerating the lock, and GitHub refuses to start a workflow whoseuses:set doesn't match its lock entries. This blockedrelease.yml,casket-pages.ymlandpush-email-notify.yml. No workflow file changes.Changes
casket-pages.yml:haskell-actions/setup@v2.12.0→@v2.12.1(the version the workflow uses)push-email-notify.yml:hyperpolymath/smtp-notify-action@v0.3.0→@v0.5.0release.yml:actions/download-artifact@v8.0.1→@v8.0.2,actions/upload-artifact@v7.0.1→@v7.0.2Each new record's commit was checked against the upstream tag with
git ls-remote. No commit an existing entry pins was changed.Testing
scripts/check-lock-sync.shreports no mismatch except thehyperpolymath/standardsreusable refs, which this PR leaves alone (see below).Not fixed here
The standards reusables (governance, hypatia-scan, secret-scanner) stay red. At the pins on
mainthey fail with "invalid lockfile pin" from standards' own old lockfile. Re-pinning to a current standards commit makes them fail at startup with zero jobs instead; I tested that on hyperpolymath/presswerk#138. That has to be fixed in standards, so this PR doesn't touch those pins.Generated by Claude Code