tbonelee opened a new pull request, #5260:
URL: https://github.com/apache/zeppelin/pull/5260

   ### What is this PR for?
   
   `zeppelin-web-angular` was on Angular 13 (end-of-life). This upgrades it to
   Angular 21 (latest), one major version at a time so each step stays small and
   reviewable. The production build, lint, and dev-server are green at every 
bump.
   
   Included:
   - Angular 13 to 21 (framework, CLI, CDK), bumped lock-step one major at a 
time
   - ng-zorro-antd to 21, adapting to its breaking changes (moved/removed entry
     points, checkbox / input-number / modal API changes, native CSS animations)
   - Pinned Node 18 to 22 (npm 8 to 10) for the frontend-maven-plugin and 
`engines`
   - ESLint 8 (eslintrc) to ESLint 9 (flat config)
   - Adopt required modern Angular APIs: built-in control flow 
(`@if/@for/@switch`),
     `provideHttpClient`, explicit zone change detection, `standalone: false` on
     NgModule declarations, RxJS 7 typing
   
   No intended functional or UI changes. This is a framework and tooling upgrade
   only. Commits are grouped per major version (and per concern within a 
version)
   so the PR can be reviewed commit by commit.
   
   ### What type of PR is it?
   Improvement
   
   ### Todos
   * [ ] Reviewer: manual smoke test of notebook / interpreter / job-manager / 
credential / theme toggle
   
   ### What is the Jira issue?
   * https://issues.apache.org/jira/browse/ZEPPELIN-6424
   
   ### How should this be tested?
   * `cd zeppelin-web-angular && npm ci`
   * Production build: `npm run build:angular` (passes)
   * Lint: `npm run lint` (passes)
   * Dev server: `npm start`, then click through the main screens to confirm 
they
     still work: open and run notebook paragraphs (all result types), the
     interpreter page, job manager, credentials, header dropdowns, and the
     dark/light theme toggle.
   
   ### Screenshots (if appropriate)
   N/A (no intended UI changes).
   
   ### Questions:
   * Does the license files need to update? No
   * Is there breaking changes for older versions? No
   * Does this needs documentation? No
   


-- 
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]

Reply via email to