The GitHub Actions job "Required Checks" on texera.git/renovate/github-actions has failed. Run started by GitHub user aglinxinyuan (triggered by aglinxinyuan).
Head commit for run: 2a2ce73cc6d933561615174fe73c29e8e790f4f6 / Xinyuan Lin <[email protected]> fix(ci): keep sbt/setup-sbt and docker/login-action on allowlisted SHAs The v1.5.7 pin for sbt/setup-sbt is not on the ASF GitHub Enterprise actions allowlist, so GitHub rejects the run while building the workflow graph: The action sbt/setup-sbt@8feba82adc7f01ddcf8165b86f778bdb5b82cebc is not allowed in apache/texera because all actions must be from a repository owned by your enterprise, created by GitHub, or match one of the patterns: ... Required Checks, Backport Checks and Benchmarks all end in startup_failure with zero jobs (build.yml is the reusable workflow the first two call), so the `Required Checks` status context is never created and the PR can never satisfy branch protection. Same failure mode as #6989, #4643 and #4344. docker/login-action v4.6.0 is reverted for the same reason: it only appears in build-and-push-images.yml, which does not run on pull_request, so PR CI cannot prove the new SHA is allowlisted — and #4344 was exactly that action's SHAs being rejected after merge. Both pins go back to the SHAs main already runs green on. The rest of the bump (Node 24.19.0, Python 3.14, the corrected sbt-dependency-submission version comment) is unchanged. Report URL: https://github.com/apache/texera/actions/runs/31468254739 With regards, GitHub Actions via GitBox
