bobbai00 opened a new pull request, #4535: URL: https://github.com/apache/texera/pull/4535
This PR is mainly to **see the effect** of upgrading the frontend to Angular 21 (from `xinyuan-angular-21`) on top of the binary-licensing work in #4387. It is **not for merge**. ## Why this PR exists The binary-licensing CI added by #4387 runs `check_binary_deps.py` against the actual production bundle (`frontend/dist/3rdpartylicenses.json`). When CI runs on this PR, the `check-npm-deps` job will print the exact `ADDED` / `STALE` deltas the Angular-21 upgrade would force into `LICENSE-binary`. That is the authoritative answer to "how much LICENSE-binary churn does the upgrade require?" ## What's in this PR - `chore/draft-binary-license` (the binary-licensing scaffolding + LICENSE-binary edits from #4387) - Merged in: `xinyuan-angular-21` (Angular 18 → 21 upgrade) - Conflict resolution: none required — both branches touch overlapping files but in non-overlapping regions, so the merge was textually clean ## What to look at 1. The `Check binary dependency licenses / Check npm dependencies` job's output — that is the bundle-scope diff against `LICENSE-binary`. 2. Static yarn.lock churn (informational, not bundle-scope): 154 added / 130 removed / 471 version-bumped. All 94 truly-new top-level packages are permissive (Category A): MIT (80), Apache-2.0 (3), BSD-3 (4), BSD-2 (2), ISC (2). Zero copyleft, zero Category X. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
