Upgrade to Angular 22 (blocked on @ngrx/signals & angular-eslint v22)

[aamcatamney]

Status: blocked on upstream

Angular 22 is published, but the project can't upgrade cleanly yet — two dependencies peer-require Angular ^21 and have no v22 release (not even prerelease, as of 2026-06-07):

Dependency	Role	Latest available
@ngrx/signals	auth signal-store (core/auth/auth.store.ts)	21.1.0 (next = 21.0.0-rc.0)
angular-eslint	lint toolchain (eslint.config.js, CI gate)	21.4.0 (canary 21.4.1-alpha)

Dependabot raised the major bumps (#72 Angular 21→22, #73 TS 6 / ESLint 10) but both failed CI at npm install with ERESOLVE:

• Angular 22 ⟂ @ngrx/signals@21.1.0 (peer @angular/core ^21)
• TypeScript 6.0 ⟂ Angular compiler-cli (peer >=5.9 <5.10); ESLint 10 unsupported by angular-eslint/typescript-eslint

Forcing it (--legacy-peer-deps) would leave ngrx + linting on unsupported peers — not worth trading a green build for. #72/#73 were closed, and .github/dependabot.yml now ignores npm semver-major so these don't recur as red PRs.

Unblock criteria

• @ngrx/signals@22 released (peers Angular ^22)
• angular-eslint@22 released

When unblocked — migration steps

1. Branch, then ng update @angular/core@22 @angular/cli@22 @angular/build@22 @angular/compiler-cli@22 (runs the official migration schematics).
2. Bump @ngrx/signals@22 and angular-eslint@22 in the same change.
3. Reassess TypeScript / ESLint majors (separate group, chore(deps-dev): Bump the other group in /ClientApp with 4 updates #73's content) against what Angular 22 + angular-eslint 22 support.
4. npm install clean (no --force), then npm run lint, npm test, ng build — fix any migration breakages.
5. Optionally re-enable npm major updates in Dependabot (revert the ignore rule) once the ecosystem tracks Angular majors closely again.

Notes

• Angular majors are now an opt-in, hand-driven migration (see the Dependabot ignore rule) — not auto-merged.