Secure GitHub Actions workflow#13569
Merged
Merged
Conversation
Contributor
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
Collaborator
|
Staged preview of the updated docs.flutter.dev site (updated for commit 9180a42): https://flutter-docs-prod--docs-pr13569-harden-workflows-vhjcjdst.web.app |
Collaborator
|
Staged preview of the updated flutter.dev site (updated for commit 9180a42): https://flutter-dev-230821--www-pr13569-harden-workflows-uba2ts40.web.app |
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
3 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.
This PR hardens the repository's GitHub Actions workflows against security risks flagged by the zizmor auditing tool. The default top-level permissions have been restricted to contents: read to enforce the principle of least privilege, and all repository checkout steps now set persist-credentials: false to prevent token leakage. A local audit verified that these updates resolve all findings with no outstanding issues.