The GitHub Actions job "Required Checks" on texera.git/release/v1.3 has failed. Run started by GitHub user github-merge-queue[bot] (triggered by github-merge-queue[bot]).
Head commit for run: d3f0529bd0d824035bcfbd46c6d6c8a2a64bd1f4 / Meng Wang <[email protected]> fix(amber, v1.3): refresh typing-extensions in LICENSE-binary-python (#8549) ### What changes were proposed in this PR? Backport of #8375 to `release/v1.3`: a clean cherry-pick of its squash commit, no adaptations. `typing-extensions` is a direct dependency and resolves to 4.16.0, while this branch's `amber/LICENSE-binary-python` still claims 4.14.1. Direct-dependency drift hard-fails the license check, so `build / pyamber (ubuntu-latest, 3.12)` is red on this branch (run 34558321985, on #8500's merge) and the `backport (release/v1.3)` check of every pyamber PR fails the same way (e.g. #8432). Re-running does not help: the resolver picks 4.16.0 each time. `amber/requirements.txt` and `amber/operator-requirements.txt` on this branch are identical to `main`'s, and after this change the manifest is byte-identical to `main`'s, where the same check is green. Opened manually by the v1.3 release manager: #8375's `release/*` labels were removed before it merged, so the automated backport never ran. Source: 16da22bab8d508e8aeebb436e2259f82d0ce7148 ### Any related issues, documentation, discussions? Backport of #8375. Originally linked #8374. ### How was this PR tested? The check itself runs in CI on this PR: a green `build / pyamber (ubuntu-latest, 3.12)` is the confirmation. Locally, the branch is verified to be exactly the squash commit cherry-picked onto `release/v1.3` (one file, one line), and the resulting `amber/LICENSE-binary-python` is byte-identical to `main`'s. ### Was this PR authored or co-authored using generative AI tooling? Yes. Generated-by: Claude Code (claude-fable-5-1) Report URL: https://github.com/apache/texera/actions/runs/35133830321 With regards, GitHub Actions via GitBox
