chore: onboard stepsecurity and apply security best practice #45
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.
Summary
This pull request introduces security and reliability improvements to the GitHub Actions workflow in
.github/workflows/master_build.yml. The main focus is on hardening the runner environment and ensuring the use of specific, pinned action versions.Detail
Security and workflow hardening:
step-security/harden-runneraction to block unwanted network egress and enforce a global allowed endpoints policy, increasing the security of the CI environment.id-token: writepermission for the dependencies job, which is required for certain secure workflows.Workflow reliability:
actions/checkout,actions/setup-java, andgradle/gradle-build-action) to use specific commit SHAs instead of version tags, reducing the risk of supply chain attacks and ensuring reproducible builds.Testing
Documentation
Requested Reviewers: @mention