mchades opened a new pull request, #11820:
URL: https://github.com/apache/gravitino/pull/11820

   ### What changes were proposed in this pull request?
   
   1. Update `.github/workflows/chart-release.yaml` and 
`.github/workflows/chart-test.yaml` to use the secure, approved commit SHA 
`9bc31f4ebc9c6b171d7bfbaa5d006ae7abdb4310` (corresponding to release tag 
`v5.0.1`) for `azure/setup-helm`.
   2. Update `.github/workflows/chart-test.yaml` to use the secure, approved 
commit SHA `829323503d1be3d00ca8346e5391ca0b07a9ab0d` (corresponding to release 
tag `v5.1.0`) for `azure/setup-kubectl`.
   3. Add a new `.github/workflows/asf-allowlist-check.yml` workflow to 
automatically check the allowlist compliance of GitHub Actions on pull requests 
modifying `.github/` directory.
   
   ### Why are the changes needed?
   
   1. The manual trigger of the `Publish Helm Charts` workflow failed because 
the Apache foundation security policy restricts third-party actions using 
version tags like `@v4.3.0`.
   2. The old commit SHA `1a275c3b69536ee54be43f2070a358922e12c8d4` previously 
used for `azure/setup-helm` has been removed from the [ASF Infrastructure 
allowed actions 
list](https://github.com/apache/infrastructure-actions/blob/main/actions.yml).
   3. The old commit SHA `15650b3ad78fff148532a140b8a4c821796b2d7b` used for 
`azure/setup-kubectl` is scheduled to expire on `2026-07-11` according to the 
allowed list, which requires an upgrade.
   4. Adding the `asf-allowlist-check` workflow helps prevent similar silent 
"startup failure" issues in the future at the PR phase.
   
   Fix: #11819
   
   ### Does this PR introduce _any_ user-facing change?
   
   No.
   
   ### How was this patch tested?
   
   This is a GitHub Actions workflow configuration change. The commit SHAs are 
verified against the ASF Actions allowed list.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to