The GitHub Actions job "Required Checks" on texera.git/gh-readonly-queue/release/v1.3/pr-8622-1736427c57a64457385fa7b47989f157837da124 has succeeded. Run started by GitHub user mengw15 (triggered by mengw15).
Head commit for run: 0f3192ea416e151ef73682e9aee33c878f79096f / Meng Wang <[email protected]> fix(deps, frontend, v1.3): update dependency @angular/core to v21.2.20 (#8622) ### What changes were proposed in this PR? Backport of #8494 to `release/v1.3`: a clean cherry-pick of its squash commit, no adaptations — three files, `frontend/package.json`, `frontend/yarn.lock` and `frontend/LICENSE-binary`. `@angular/core` 21.2.19 → 21.2.20 fixes CVE-2026-88057 (GHSA-hh8m-fm6v-7cvg). This branch is still on 21.2.19, so v1.3 would ship with it unpatched. `@angular/common` and `@angular/compiler` stay at 21.2.19 here, exactly as on `main`; their own bumps are #8492 and #8493, still open. Opened manually by the v1.3 release manager: the automated fast path cherry-picked this cleanly and then pushed it straight to `release/v1.3`, where the Merge Queue ruleset rejected the push (`GH013`, [run 35293784997](https://github.com/apache/texera/actions/runs/35293784997)). The Actions-app bypass meant to unblock that path (#8379) was never created — asfyaml rejects an `Integration` bypass actor — and the failing job's notification 403s for want of `pull-requests: write`, so the loss left neither a backport PR nor a comment on #8494. The `release/v1.2` backport did get a PR (#8584, still draft) only because its cherry-pick conflicted and so took the other code path. See #8377. Source: 8284b4280c4cd988a4b072900fb7dca7b89cf56b ### Any related issues, documentation, discussions? Backport of #8494. ### How was this PR tested? The change is a dependency bump identical to #8494; the backport tree is verified byte-identical to cherry-picking the squash commit onto `release/v1.3`, and the resulting `frontend/package.json` reads `"@angular/core": "21.2.20"`. Release-branch CI runs the frontend matrix on this PR. ### Was this PR authored or co-authored using generative AI tooling? Yes. Generated-by: Claude Code (claude-opus-5) Co-authored-by: Mend Renovate <[email protected]> Co-authored-by: Xuan Gu <[email protected]> Report URL: https://github.com/apache/texera/actions/runs/35651667768 With regards, GitHub Actions via GitBox
