Yicong-Huang opened a new issue, #6989: URL: https://github.com/apache/texera/issues/6989
## Summary All CI on `release/v1.2` is currently broken: the **Required Checks** workflow ends in `startup_failure` and never runs, so no build/test checks appear on v1.2 PRs and the label-based stack selection never executes. ## Root cause `release/v1.2`'s workflows pin `sbt/setup-sbt` at an old SHA that is **not on the ASF GitHub Enterprise actions allowlist**: ``` sbt/setup-sbt@508b753e53cb6095967669e0911487d2b9bc9f41 # v1.1.22 ``` GitHub rejects the run while building the workflow graph, with: > The action `sbt/setup-sbt@508b753e53cb6095967669e0911487d2b9bc9f41` 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: … Because the failure happens at startup, the `precheck` job never runs — which is why CI "does not trigger by label" on v1.2 PRs. `main` already uses the allowlisted version and its Required Checks is green: ``` sbt/setup-sbt@6444f4c8111de4b9059c3975def104b03cfaa5f0 # v1.5.2 ``` (`main` reached v1.5.2 via #6710 / `d28b761ae`.) ## Timeline - `release/v1.2` push CI was green through 2026-07-24. - Since 2026-07-28 every `release/v1.2` run (push + PR) is `startup_failure` — matching when the enterprise allowlist no longer accepted the old pin. ## Proposed fix Bump `sbt/setup-sbt` on `release/v1.2` from `@508b753e… # v1.1.22` to the allowlisted `@6444f4c8111de4b9059c3975def104b03cfaa5f0 # v1.5.2`, matching `main`. Affected files on `release/v1.2` (6 occurrences): - `.github/workflows/build.yml` — 3 - `.github/workflows/build-and-push-images.yml` — 3 This is a minimal, targeted change rather than backporting the large github-actions group bump (#6187), which touches 15 actions across 17 files and conflicts heavily against v1.2. ## Impact / blocked work - All `release/v1.2` CI is blocked. - Backport PRs against v1.2 cannot get green Required Checks, e.g. #6982 and #6984. ## Follow-up Worth a quick audit of the remaining action pins on `release/v1.2` against the enterprise allowlist so the next run doesn't fail on a different disallowed 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]
