chore: removed cache usage from release workflow to prevent Supply Chain attack #205
Conversation
This file contains 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
lquixada
force-pushed
the
cache-removed-from-release
branch
from
ed8d967 to
ba8f356
Compare
lquixada
force-pushed
the
cache-removed-from-release
branch
from
f6887f8 to
cba6783
Compare
lquixada
force-pushed
the
cache-removed-from-release
branch
from
cba6783 to
c99c990
Compare
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 addresses a security issue called GitHub Action Pwn Request in the release workflow. It removes all cache steps to prevent cache poisoning from malicious pull requests. Here's more info on how that works.
This was pointed out in a report provided by Roni Carta and Adnan Khan. Kudos to them!