fix(deps, ci, v1.2): bump sbt/setup-sbt to v1.5.7 to restore CI - #7716
Open
github-actions[bot] wants to merge 2 commits into
Open
fix(deps, ci, v1.2): bump sbt/setup-sbt to v1.5.7 to restore CI#7716github-actions[bot] wants to merge 2 commits into
github-actions[bot] wants to merge 2 commits into
Conversation
### What changes were proposed in this PR? CI has been red repo-wide since 2026-08-16 ~02:00 UTC — `main`, the merge queue, and every PR that runs a Scala stack. The jobs die in 3–7s during *Prepare all required actions*, before checkout, so they produce no test output at all. The cause is the ASF actions allowlist, not anything in this repository. `sbt/setup-sbt` reaches a nested `carabiner-dev` action that is no longer permitted: ``` .github/workflows/*.yml └─ sbt/setup-sbt@6444f4c v1.5.2 allowed └─ carabiner-dev/actions@94f2939 v1.2.1 allowed └─ carabiner-dev/actions@2a11d59 v1.1.7 BLOCKED ``` > The action carabiner-dev/actions@2a11d59 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: … Nothing in the tree changed — every link in that chain is SHA-pinned, and the `sbt/setup-sbt` pin last moved in #6710 on 2026-07-22. The same `2a11d59` downloaded successfully at `2026-08-15T02:01Z` (#7674's amber job) and is rejected at `2026-08-17T02:13Z`. Last clean run before the break: merge-queue `pr-7699` at `2026-08-16T01:52:00Z`; first failure: `main` at `2026-08-16T02:04:42Z`. This bumps all 9 call sites from v1.5.2 to v1.5.7, which resolves down a different path: | | v1.5.2 (current) | v1.5.7 (this PR) | | --- | --- | --- | | `ampel/verify` | `94f2939` (v1.2.1) | `36a39ef` (v1.2.6) | | `install/ampel` | **`2a11d59` — blocked** | `2fec8bd8` | | `install/bnd` | `2a11d59` | no longer referenced | Call sites: `benchmarks.yml` (1), `build-and-push-images.yml` (3), `build.yml` (4), `dependency-graph.yml` (1). > Reviewer note — one thing I could not verify up front. The org allowlist is not readable without repo-admin (`403`), and the error message truncates the pattern list before the `carabiner-dev` entries, so I could not confirm in advance that `2fec8bd8` is permitted. **This PR's own CI run is the experiment.** If it fails on the same error, the bump is a dead end and the fallback is an INFRA request to re-allow `carabiner-dev/actions@2a11d59a135c5e291f305f249a92ad7903e3ee0f`. ### Any related issues, documentation, discussions? No issue filed — the regression originates outside the repository and this PR is the unblock. The previous bump of this pin was #6710. ### How was this PR tested? By this PR's CI, which is the only place the failure reproduces — it depends on the `apache/texera` actions policy and cannot be triggered locally or on a fork. The change touches `.github/**`, so the labeler applies `ci`, and `ci` maps to every stack in `LABEL_STACKS` (`.github/workflows/precheck.yml`) — `frontend`, `amber`, `amber-integration`, `platform`, `platform-integration`, `pyamber`, `agent-service`, `infra`, `pyright-language-service` — plus `Bench`. Every job that consumes `sbt/setup-sbt` is therefore exercised here. ### Was this PR authored or co-authored using generative AI tooling? (backported from commit 7a2c8d0) Generated-by: Claude Code (Claude Opus 5)
Contributor
Author
|
The cherry-pick conflicted and was committed with conflict markers. Resolve the conflicts on this branch, then mark this PR ready for review. Conflicting files:
|
release/v1.2 has neither benchmarks.yml nor dependency-graph.yml, and its build.yml has no platform-integration job, so the cherry-pick hit a modify/delete on all three and pulled the main-only content in wholesale. Dropped both foreign workflows and took the HEAD side of the platform-integration hunk. What remains is the six pin bumps that exist on this branch: build.yml x3, build-and-push-images.yml x3.
Contributor
Author
Automated Reviewer SuggestionsBased on the
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## release/v1.2 #7716 +/- ##
==================================================
- Coverage 53.00% 52.96% -0.04%
+ Complexity 2542 2539 -3
==================================================
Files 1078 1078
Lines 42366 42366
Branches 4565 4565
==================================================
- Hits 22454 22441 -13
- Misses 18593 18600 +7
- Partials 1319 1325 +6
*This pull request uses carry forward flags. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
aglinxinyuan
marked this pull request as ready for review
August 17, 2026 05:28
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this PR?
Automated backport of #7710 to
release/v1.2.Source: 7a2c8d0 · automation run
Any related issues, documentation, discussions?
Backport of #7710.
How was this PR tested?
Release-branch CI runs on this branch once the conflicts are resolved and this PR is marked ready for review.
Was this PR authored or co-authored using generative AI tooling?
No.