xuang7 opened a new pull request, #6398:
URL: https://github.com/apache/texera/pull/6398
### What changes were proposed in this PR?
Backport of #6235 to `release/v1.2` (cherry-pick of the change from #6268,
which applies cleanly on the current branch head).
| Package | Before | After |
| --- | --- | --- |
| `@ngx-formly/core` | `6.3.12` | `7.1.0` |
| `@ngx-formly/ng-zorro-antd` | `6.3.12` | `7.1.0` |
Both packages ship from the same monorepo and must stay in lock-step:
`ng-zorro-antd`'s `peerDependency` pins `core` to an exact version, and its
fesm bundle imports internal `ɵ`-prefixed symbols from `core`.
`frontend/LICENSE-binary` and `yarn.lock` are updated accordingly.
### Why backport this?
#6268 was closed with the question unanswered ("is it related to a security
concern?"). It is not a CVE fix — it is a **runtime bug fix**: a UI bug was
found during **v1.2.0-incubating RC2 validation**.
Root cause: `release/v1.2` ships **Angular 21.2.17** with **@ngx-formly
6.3.12**. The formly 6.x line does not support Angular 21 — 7.x is the
Angular-21-compatible line. Formly renders the operator properties panel, so
this incompatibility breaks form rendering in the workflow editor at runtime.
### Any related issues, documentation, discussions?
- Original PR on `main`: #6235 (merged)
- Previous backport attempt: #6268 (closed pending justification)
### How was this PR tested?
Cherry-picked commit is identical to #6268, which passed CI. Frontend CI on
this PR will re-verify the build against the current `release/v1.2` head.
Manual verification of the operator properties panel should be part of RC3
validation.
### Was this PR authored or co-authored using generative AI tooling?
Co-authored with Claude (Fable 5)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
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]
