Skip to content

ci(actions-lock): bring actions.lock back in line with the workflows - #139

Merged
hyperpolymath merged 1 commit into
mainfrom
ci/actions-lock-repair
Oct 27, 2026
Merged

hyperpolymath merged 1 commit into
mainfrom
ci/actions-lock-repair

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Summary

actions.lock had drifted from the workflow files. Dependabot bumped actions in the YAML without regenerating the lock, and GitHub refuses to start a workflow whose uses: set doesn't match its lock entries. This blocked release.yml, casket-pages.yml and push-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.0
  • release.yml: actions/download-artifact@v8.0.1 → @v8.0.2, actions/upload-artifact@v7.0.1 → @v7.0.2
  • New records for those four refs, and the four old records removed now that nothing references them

Each new record's commit was checked against the upstream tag with git ls-remote. No commit an existing entry pins was changed.

Testing

  • standards' scripts/check-lock-sync.sh reports no mismatch except the hyperpolymath/standards reusable refs, which this PR leaves alone (see below).
  • Every lock entry has a dependency record.

Not fixed here

The standards reusables (governance, hypatia-scan, secret-scanner) stay red. At the pins on main they 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

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
@coderabbitai

coderabbitai Bot commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters: 1
  • .github/workflows/actions.lock is excluded by !**/*.lock

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 1f2b0d83-3937-4e02-9bdc-016ed6145a9c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • No new commits to review - use @coderabbitai full review for a full pass
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@linear-code
linear-code Bot marked this pull request as ready for review October 27, 2026 01:33

Copy link
Copy Markdown
Owner Author

CI note: the red checks on this PR don't come from this change. The PR edits only .github/workflows/actions.lock.

  • lint-workflows: .github/workflows/*.yml missing SPDX header. It fails the same way on main. Fixing it means adding SPDX headers to the workflow files, which belongs outside this PR.
  • governance / hypatia-scan / secret-scanner / rust-ci (0 jobs): the standards reusable workflows have started zero jobs from callers estate-wide since about 2026-10-25 19:30 UTC, including on main. Here main broke on a Dependabot merge that changed only the codeql and trufflehog lock entries. This PR doesn't touch those workflows' lock entries; the fix belongs in the standards repo.
  • test.yml: startup_failure on main too, in every run since at least 2026-10-08.

No fix exists yet for any of these, so I haven't ported one.


Generated by Claude Code

@hyperpolymath
hyperpolymath enabled auto-merge (squash) October 27, 2026 01:53
@coderabbitai

coderabbitai Bot commented Oct 27, 2026

Copy link
Copy Markdown
Contributor

Add Carrot credits or activate Agent usage billing to use Autofix

@hyperpolymath
hyperpolymath merged commit a2bc8b8 into main Oct 27, 2026
18 of 20 checks passed
@hyperpolymath
hyperpolymath deleted the ci/actions-lock-repair branch October 27, 2026 02:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants