Pin third-party Actions - #21
Merged
Merged
Conversation
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.
What changed
subosito/flutter-action@v2use to the current immutablev2commitandroid-actions/setup-android@v4use to the current immutablev4commitWhy
CodeQL opened six medium-severity
actions/unpinned-tagalerts. Moving action tags can be retargeted upstream, while full commit SHAs make workflow dependencies immutable.The first CI attempt exposed two source-guard expectations that still required the old moving Android tag. Those guards now enforce the pinned revisions instead.
Impact
Workflow behavior and configured tool versions are unchanged. The same upstream action revisions are now referenced by SHA.
Validation
git diff --checkv2andv4tag refs