chore: onboard stepsecurity and apply security best practice #17
+9
−1
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 pull request introduces security enhancements to the CI workflow by hardening the runner and specifying permissions. The most important changes are:
Security improvements to the CI workflow:
step-security/harden-runneraction to thelint-and-testjob in.github/workflows/ci.ymlto block egress traffic and enforce a global allowed endpoints policy, improving runner security.id-token: writepermission for thelint-and-testjob, aligning with best practices for least privilege.Dependency version pinning:
actions/checkoutaction to use a specific commit hash (v3.6.0) instead of a floating version, ensuring reproducibility and security.