Repository navigation
ci: pin actions to commit shas - #5
Merged
Merged
Conversation
These were the last tag-pinned action references in the org. A tag can be moved to new code; a commit SHA cannot, and the org is about to require SHA pinning, which would stop this workflow from running. Same versions as before; Renovate keeps the SHAs current.
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.
Pins actions/checkout v4, astral-sh/setup-uv v6 and extractions/setup-just v3 to the commits those tags point to today. Same versions, no behaviour change.
These were the last tag-pinned action references anywhere in the org (a grep of every repo's workflows on main), and the org is about to require SHA pinning, which would block this workflow from running.