You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All CI on release/v1.2 is 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 (precheck) never executes — which is why CI appears to "not trigger by label" on v1.2 PRs.
Root cause: release/v1.2 pins sbt/setup-sbt at a SHA that is not on the ASF GitHub Enterprise actions allowlist:
GitHub rejects the run while building the workflow graph:
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: …
Expected: Required Checks starts and runs the label-gated build/test stacks on release/v1.2, same as on main.
main already uses the allowlisted version and its Required Checks is green:
Fix: bump the 6 sbt/setup-sbt pins on release/v1.2 from @508b753e… # v1.1.22 to @6444f4c8111de4b9059c3975def104b03cfaa5f0 # v1.5.2, in .github/workflows/build.yml (×3) and .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: all release/v1.2 CI is blocked, including backport PRs #6982 and #6984.
Follow-up: worth auditing the remaining action pins on release/v1.2 against the enterprise allowlist so the next run doesn't fail on a different disallowed action.
What happened?
All CI on
release/v1.2is broken. The Required Checks workflow ends instartup_failureand never runs, so no build/test checks appear on v1.2 PRs and the label-based stack selection (precheck) never executes — which is why CI appears to "not trigger by label" on v1.2 PRs.Root cause:
release/v1.2pinssbt/setup-sbtat a SHA that is not on the ASF GitHub Enterprise actions allowlist:GitHub rejects the run while building the workflow graph:
Expected: Required Checks starts and runs the label-gated build/test stacks on
release/v1.2, same as onmain.mainalready uses the allowlisted version and its Required Checks is green:(
mainreached v1.5.2 via #6710 /d28b761ae.)Fix: bump the 6
sbt/setup-sbtpins onrelease/v1.2from@508b753e… # v1.1.22to@6444f4c8111de4b9059c3975def104b03cfaa5f0 # v1.5.2, in.github/workflows/build.yml(×3) and.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: all
release/v1.2CI is blocked, including backport PRs #6982 and #6984.Follow-up: worth auditing the remaining action pins on
release/v1.2against the enterprise allowlist so the next run doesn't fail on a different disallowed action.How to reproduce?
release/v1.2(e.g. fix(docs, v1.2): Add missing license headers to Docs #6982, fix(deps, frontend, v1.2): update dependency ajv to v8.18.0 [security] #6984), or push torelease/v1.2.startup_failurewith no jobs — e.g. https://github.com/apache/texera/actions/runs/30417060865sbt/setup-sbt@508b753e…action.Started 2026-07-28;
release/v1.2push CI was green through 2026-07-24.Version/Branch
1.2.0-incubating (release/v1.2)
Commit Hash (Optional)
2bcb9aa (current
release/v1.2tip at time of filing)