All 5 open Dependabot PRs are blocked behind an Angular 16→19 / Nx upgrade

I went through the five open Dependabot PRs to consolidate them and could not land any. Each is blocked by the repo's own tooling versions rather than by anything in the bump itself, so here is what I verified.

The baseline is healthy, for the record: npm ci, npm run lint, npm run test and npm run build all pass on master as-is.

cypress 13 — #630, #561

This looked like the one standalone bump, but:

@nx/cypress@16.3.2  peerDependencies.cypress: >= 3 < 13

npm refuses cypress 13 while @nx/cypress is on 16.x, so #630 needs an Nx upgrade first. #561 rides along with it (@cypress/request 3.x only ships inside cypress 13+).

@angular/cdk 19 — #631, and @angular-eslint 19 — #628

The app is on @angular/core@^16.2.7 / @angular/material@^16.2.7. @angular/cdk@19 requires Angular 19, so #631 is really "Angular 16 → 19" — three majors, with the CDK and Material migrations that come with them. #628 (@angular-eslint/template-parser 17 → 19) is the same story on the lint side.

@nx/linter 19 — #609

@nx/linter was renamed to @nx/eslint in Nx 18; the package Dependabot is bumping is a deprecated shim. This should not be bumped to 19 — it should be replaced by @nx/eslint as part of the Nx migration.

The underlying problem: the tooling is already split across three majors

This is worth fixing before any of the above, because it is what makes each bump land awkwardly:

Nx spans 16, 17 and 19 simultaneously, and the Angular devkit is ahead of Angular itself.

Suggested order

1. npx nx migrate latest to bring the whole Nx set onto one major, swapping @nx/linter → @nx/eslint. That should also unblock cypress 13.
2. ng update @angular/core @angular/cli one major at a time, 16 → 17 → 18 → 19, then @angular/material/@angular/cdk and @angular-eslint.
3. Re-run the five Dependabot PRs; most should become no-ops.

I left all five open and made no changes to the repo.

Start with the dependency versions listed in the issue and run npx nx migrate latest, then follow the Angular 16 → 17 → 18 → 19 update sequence. Re-run npm ci, npm run lint, npm run test, and npm run build after the migrations, then check whether the five Dependabot PRs can land or have become no-ops.