chore(BLUE-129): pin actions versions #36
Merged
Conversation
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
DamienVoreiter
approved these changes
Jun 6, 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.
At Doctolib, we already had a strong security posture on our GitHub Actions, but following the tj-actions repository compromission and the disclosure of CVE-2025-30066, we are forced to do even better! 💪 We want to pin all external GitHub Actions versions we use to a commit SHA-1 instead of a floating tag that can still be overridden by a malicious actor.
FYI, the clippy-check action used in another workflow is not present in our allowlist and thus cannot be used today. It was also deprecated by the maintainers so we might want to change that.
https://github.com/actions-rs/clippy-check