Repository navigation
chore: pin actions to commit SHAs - #193
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
kim-em
added a commit
that referenced
this pull request
Oct 2, 2026
Resolve the CHANGELOG conflict with the SHA pinning of #193, and pin the checkout steps this PR adds to the same SHA. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
kim-em
added a commit
that referenced
this pull request
Oct 2, 2026
Resolve the CHANGELOG conflict with the SHA pinning of #193, and pin the checkout steps this PR adds to the same SHA. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
This PR pins the
actions/cachesteps inaction.yml, and every action used by this repository's workflows, to full commit SHAs, keeping the previous tag as a trailing comment. Organizations that require SHA-pinned actions (as leanprover-community is about to) reject unpinned actions anywhere in the chain, including insidelean-action, so everylean-actionuser there currently fails at job setup.🤖 Prepared with Claude Code