You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: add Angular 22 support (non-breaking, keeps 18β21) (#212)
* feat: add support for Angular 22
Extends the supported Angular range from 18β21 to 18β22.
- package.json: bump devkit upper bounds (architect <0.2300.0,
core/schematics <23.0.0) and the @angular/cli peer to <23.0.0; v3.1.0
- README: update supported range to "Angular 18 to 22"
- CI: add an Angular 22 ng new / ng add / ng deploy smoke test
- tests: add angular-22.json fixture (real ng new v22.0.0 output) plus
Angular 22 compatibility assertions
No engine/builder changes needed: Angular 22's generated angular.json is
structurally identical to 21 (@angular/build:application, no outputPath),
which actions.ts already handles.
* chore: port Node version range improvement from #211#211 rightly flagged that engines.node ">=18.0.0" is stale β no supported
Angular actually runs on Node 18.0β18.18 (Angular 18's real floor is
18.19.1). It set "^20.19.0 || ^22.12.0 || >=24.0.0", but that is Angular
20/21's requirement and is too narrow here: it locks out Node 18/19 needed
by the Angular 18/19 users this PR still supports, plus odd majors.
Bump to a wide lower bound at the true floor of the oldest supported
Angular (18 β 18.19.1). Angular CLI enforces its own stricter per-version
Node gate, so we only need a sane floor, not a duplicate of it.
* ci: run "Build and test" on pull requests + enable manual dispatch
The workflow only triggered on push to main/big-update, so pull requests
(including this one) received no CI at all. Add a pull_request trigger
(targeting main) so PRs are validated before merge, plus workflow_dispatch
for on-demand runs (becomes usable once this lands on the default branch).
* ci: drop completed big-update branch from push triggers
0 commit comments