bharos opened a new pull request, #143: URL: https://github.com/apache/gravitino-site/pull/143
### What changes were proposed in this pull request? Pins `pnpm/action-setup` in `.github/workflows/deploy.yml` to `0977fd99725f1db4007ccb2928dbb4e90d06cc86` (v6.0.10), the SHA already used by `apache/gravitino`. ### Why are the changes needed? The Deploy workflow has been failing at startup since July with: > The action pnpm/action-setup@v4 is not allowed in apache/gravitino-site because all actions must be from a repository owned by your enterprise, created by GitHub, or match one of the patterns: ... Because Deploy never starts, nothing has been published to `asf-site` since 2026-07-01, so the live site is stale — the 1.3.1 release notes and download links are merged to `main` but not visible on gravitino.apache.org. `apache/gravitino` hit the same policy and fixed it the same way in [#12899](https://github.com/apache/gravitino/issues/12899); this uses the identical SHA and keeps `version: 9`, which is what that repo runs today. ### Does this PR introduce any user-facing change? No — CI only. It does unblock publishing the already-merged site content. ### How was this patch tested? The Deploy run on this PR is the test: if the action is now allowlisted, the workflow starts instead of failing at 0s. `package.json` has no `packageManager` field, so the `version: 9` input remains valid for the newer action. -- 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]
