Repository navigation
ci(actions-lock): lock the SLSA generator call - #165
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. - `generator-generic-ossf-slsa3-publish.yml`: add the missing entry `slsa-framework/slsa-github-generator@f7dd8c54c2067bafc12ca7a55595d5ee9b75204a` - new record `slsa-framework/slsa-github-generator@f7dd8c54c2067bafc12ca7a55595d5ee9b75204a` (ref `v2.1.0`, commit `f7dd8c54c206…`) 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
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
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 |
Summary
generator-generic-ossf-slsa3-publish.ymlcallsslsa-framework/slsa-github-generator@f7dd8c54…as a job-level reusable, butactions.lockhad neither an entry nor a record for it. GitHub refuses to start a workflow whoseuses:set doesn't match its lock entries. No workflow file changes.Changes
generator-generic-ossf-slsa3-publish.yml: add the missing entryslsa-framework/slsa-github-generator@f7dd8c54c2067bafc12ca7a55595d5ee9b75204aref: 'v2.1.0',owner_id: 80431187,repo_id: 475074978. That is the taggit ls-remoteshows peeling tof7dd8c54, and the IDs seven other estate lockfiles record for this action.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, rust-ci) 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