Skip to content

fix(ci): bump sbt/setup-sbt to v1.1.22 in generate-jooq job#4644

Merged
bobbai00 merged 2 commits into
apache:mainfrom
bobbai00:fix/build-and-push-image
May 2, 2026
Merged

fix(ci): bump sbt/setup-sbt to v1.1.22 in generate-jooq job#4644
bobbai00 merged 2 commits into
apache:mainfrom
bobbai00:fix/build-and-push-image

Conversation

@bobbai00
Copy link
Copy Markdown
Contributor

@bobbai00 bobbai00 commented May 2, 2026

What changes were proposed in this PR?

Bumps sbt/setup-sbt in the generate-jooq job of .github/workflows/build-and-push-images.yml from the v1.1.14 SHA (3e125ece…) to the v1.1.22 SHA (508b753e…), matching the SHA already used by the build-amd64 and build-arm64 jobs.

The v1.1.14 SHA is no longer on ASF Infra's allowlist, so the workflow currently fails immediately 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

Since generate-jooq is a needs: of both build jobs, this single mismatch blocks the entire workflow.

Any related issues, documentation, discussions?

Closes #4643

How was this PR tested?

Will be verified by triggering the Build and push images workflow on workflow_dispatch once merged. The change is a one-line action SHA bump aligning with SHAs already validated by the parallel build jobs.

Was this PR authored or co-authored using generative AI tooling?

Generated-by: Claude Code (Opus 4.7)

The v1.1.14 SHA in generate-jooq is no longer allowlisted by ASF Infra,
which fails the whole build-and-push-images workflow. Aligns with the
SHA already used by build-amd64 and build-arm64.

Closes apache#4643

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@github-actions github-actions Bot added fix ci changes related to CI labels May 2, 2026
@Yicong-Huang Yicong-Huang added the release/v1.1.0-incubating back porting to release/v1.1.0-incubating label May 2, 2026
@bobbai00 bobbai00 enabled auto-merge (squash) May 2, 2026 04:00
@bobbai00 bobbai00 merged commit 61ce334 into apache:main May 2, 2026
26 checks passed
github-actions Bot pushed a commit that referenced this pull request May 2, 2026
### What changes were proposed in this PR?

Bumps `sbt/setup-sbt` in the `generate-jooq` job of
`.github/workflows/build-and-push-images.yml` from the v1.1.14 SHA
(`3e125ece…`) to the v1.1.22 SHA (`508b753e…`), matching the SHA already
used by the `build-amd64` and `build-arm64` jobs.

The v1.1.14 SHA is no longer on ASF Infra's allowlist, so the workflow
currently fails immediately 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

Since `generate-jooq` is a `needs:` of both build jobs, this single
mismatch blocks the entire workflow.

### Any related issues, documentation, discussions?

Closes #4643

### How was this PR tested?

Will be verified by triggering the `Build and push images` workflow on
`workflow_dispatch` once merged. The change is a one-line action SHA
bump aligning with SHAs already validated by the parallel build jobs.

### Was this PR authored or co-authored using generative AI tooling?

Generated-by: Claude Code (Opus 4.7)

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

(backported from commit 61ce334)
SarahAsad23 pushed a commit to SarahAsad23/texera that referenced this pull request May 4, 2026
)

### What changes were proposed in this PR?

Bumps `sbt/setup-sbt` in the `generate-jooq` job of
`.github/workflows/build-and-push-images.yml` from the v1.1.14 SHA
(`3e125ece…`) to the v1.1.22 SHA (`508b753e…`), matching the SHA already
used by the `build-amd64` and `build-arm64` jobs.

The v1.1.14 SHA is no longer on ASF Infra's allowlist, so the workflow
currently fails immediately 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

Since `generate-jooq` is a `needs:` of both build jobs, this single
mismatch blocks the entire workflow.

### Any related issues, documentation, discussions?

Closes apache#4643

### How was this PR tested?

Will be verified by triggering the `Build and push images` workflow on
`workflow_dispatch` once merged. The change is a one-line action SHA
bump aligning with SHAs already validated by the parallel build jobs.

### Was this PR authored or co-authored using generative AI tooling?

Generated-by: Claude Code (Opus 4.7)

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci changes related to CI fix release/v1.1.0-incubating back porting to release/v1.1.0-incubating

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Build and push images workflow fails: sbt/setup-sbt action SHA not allowlisted

2 participants