What happened?
The Build and push images workflow fails at the generate-jooq job with:
The action sbt/setup-sbt@3e125ece5c3e5248e18da9ed8d2cce3d335ec8dd is not allowed in apache/texera because all actions must be from a repository owned by your enterprise
ASF Infra's allowlist no longer permits the v1.1.14 SHA pinned in generate-jooq. The other two jobs (build-amd64, build-arm64) already use the allowlisted v1.1.22 SHA, so only the JOOQ job is blocked — but it is a needs: of both build jobs, so the whole workflow fails.
Expected: workflow runs to completion and publishes images for all services.
How to reproduce?
- Trigger
.github/workflows/build-and-push-images.yml (manual or nightly).
- The
generate-jooq job fails immediately on the Setup sbt launcher step.
Version
1.1.0-incubating (Pre-release/Master)
Relevant log output
The action sbt/setup-sbt@3e125ece5c3e5248e18da9ed8d2cce3d335ec8dd is not allowed in apache/texera because all actions must be from a repository owned by your enterprise
What happened?
The
Build and push imagesworkflow fails at thegenerate-jooqjob with:ASF Infra's allowlist no longer permits the
v1.1.14SHA pinned ingenerate-jooq. The other two jobs (build-amd64,build-arm64) already use the allowlistedv1.1.22SHA, so only the JOOQ job is blocked — but it is aneeds:of both build jobs, so the whole workflow fails.Expected: workflow runs to completion and publishes images for all services.
How to reproduce?
.github/workflows/build-and-push-images.yml(manual or nightly).generate-jooqjob fails immediately on theSetup sbt launcherstep.Version
1.1.0-incubating (Pre-release/Master)
Relevant log output