chore: remove actions.lock.yaml - #17
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
dyl-sv
approved these changes
Sep 29, 2026
dyl-sv
left a comment
dyl-sv
left a comment
There was a problem hiding this comment.
Confirmed this PR only deletes the deprecated .github/actions.lock.yaml (no other changes). Approving as part of the org-wide actions.lock.yaml cleanup.
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
2 participants
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.
.github/actions.lock.yamlis a generated report artifact, not a source of truth: nothing in CI reads it, and it drifts out of date as soon as workflows change (many copies still list actions the workflows no longer use). Removing it from VCS.No workflow or runtime behaviour changes.
🤖 Generated with Claude Code