Pin actions, reduce permissions and third-party actions#2222
Open
sethmlarson wants to merge 1 commit intopypa:masterfrom
Open
Pin actions, reduce permissions and third-party actions#2222sethmlarson wants to merge 1 commit intopypa:masterfrom
sethmlarson wants to merge 1 commit intopypa:masterfrom
Conversation
Member
|
Something in the changes for build distributions has broken, my guess is it is the switch from inputs.version to the env_var for the uv install. |
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.
Hello! I'm auditing PyPA GitHub Action release workflows using Zizmor. Here's the changes I recommend :) Let me know if you'd prefer I break these out into separate PRs.
pull_request_targetwhich has caused multiple injections of malware already. This assumes that auto-merge already gates on CI/branch protections?contents: readis enough since separate permissions are set for when GitHub Releases are created or PyPI uploads occur.gh release create.I'll be around when the next release happens, so if stuff breaks I can help pick up the pieces. I understand release workflows are difficult to test :(