Repository navigation
ci(actions-lock): bring actions.lock back in line with the workflows - #122
Merged
Merged
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` - `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`) - new record `hyperpolymath/smtp-notify-action@v0.5.0` (ref `v0.5.0`, commit `c1c9fa07992a…`) - new record `slsa-framework/slsa-github-generator@f7dd8c54c2067bafc12ca7a55595d5ee9b75204a` (ref `v2.1.0`, commit `f7dd8c54c206…`) - 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
 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
|
Add Carrot credits or activate Agent usage billing to use Autofix |
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.
Summary
actions.lockhad drifted from the workflow files. 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 entry and record forslsa-framework/slsa-github-generator@f7dd8c54…, withref: 'v2.1.0'and the IDs seven other estate lockfiles record for this actionpush-email-notify.yml:hyperpolymath/smtp-notify-action@v0.3.0→@v0.5.0(the version the workflow uses), with a new record and the old one removedEach 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
coverage.yml: no lock change was needed. If it is still blocked after this, the cause is something else.Generated by Claude Code