Don't use cache in CI. #6985
Open
Don't use cache in CI. #6985
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
|
I'm sorry, but it requires further explanation of the reasons why. |
|
The update of zizmor has a new error: error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack. See https://woodruffw.github.io/zizmor/audits/#cache-poisoning and https://woodruffw.github.io/zizmor/audits/#remediation_13 for the details. It suggests removing all caching. |
|
yeah, but I think it is unlikely + they recommend disabling it for release workflows. |
|
I removed it everywhere zizmor was complaining about it. I think that was everywhere in CICD.yml. It says you ought to remove it everywhere you intend to publish build artifacts. |
|
yeah, but i am not convinced we should follow the tool blindly :) |
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.
No description provided.