Chore: Pin actions to specific versions #17
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
The tj-actions/changed-files repository had a compromise on March 14, 2025. The attacker was able to push a new version of the repository that allowed exfiltration of secrets in use during the workflow. GitHub temporarily disabled the repository and the owner has since restored it. This repository was affected but only exfiltratred secrets were short lived, workflow time only. No secret rotations are necessary. To help prevent this in the future, LF Release Engineering is providing this change to meet best practices so that future incidents like this can be mitigated. Reference: GHSA-mrrh-fwg8-r2c3 Signed-off-by: Andrew Grimberg <[email protected]>
eb-oss
approved these changes
Mar 17, 2025
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.
The tj-actions/changed-files repository had a compromise on March 14,
2025. The attacker was able to push a new version of the repository that
allowed exfiltration of secrets in use during the workflow. GitHub
temporarily disabled the repository and the owner has since restored it.
This repository was affected but only exfiltratred secrets were short
lived, workflow time only. No secret rotations are necessary.
To help prevent this in the future, LF Release Engineering is providing
this change to meet best practices so that future incidents like this
can be mitigated.
Reference: GHSA-mrrh-fwg8-r2c3
Signed-off-by: Andrew Grimberg [email protected]