feat(sanity)!: add Angular 20 support#56
Merged
Conversation
Expand Angular peer compatibility to include v20 and update the workspace Angular test/build toolchain. BREAKING CHANGE: mark the Angular 20 compatibility update as a breaking release for package consumers.
✅ Deploy Preview for limitless-angular-sanity-example canceled.
|
commit: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Checklist
Updates Angular compatibility for
@limitless-angular/sanityto include Angular 20.Closes # N/A
What is the new behavior?
@angular/common,@angular/core, and@angular/routerto include Angular 20.angular-eslint,ng-packagr, and example app manifests for the Angular 20 toolchain.provideZonelessChangeDetection/ Analog'ssetupTestBed({ zoneless: true })test setup.@testing-library/angularto v18 and removes no-longer-needed direct dev dependencies such as@angular-devkit/architectand@angular/platform-browser-dynamicfrom the package manifest.selecttooptionSelectedto satisfy Angular ESLint 20 output naming rules.Does this PR introduce a breaking change?
Marked as breaking through the Conventional Commit
!indicator andBREAKING CHANGEcommit footer. Existing Angular 18 and 19 peer support remains declared, but the workspace build/test toolchain and compatibility build target move to Angular 20.Other information
Validation run:
pnpm installnode --test tools/angular-compat/*.test.mjspnpm run compat:assertpnpm run compat:matrixpnpm run compat:packpnpm run compat:artifactpnpm run compat:test --angular 20pnpm run compat:test --set angular-20-floorpnpm --filter @limitless-angular/sanity testpnpm --filter @limitless-angular/sanity buildpnpm run testpnpm run lintpnpm run buildNotes:
pnpm run lintpasses with the repo's existing unused Angular ESLint disable warnings.pnpm run buildpasses with existing CommonJS optimization and Browserslist warnings in the example apps.[Optional] What gif best describes this PR or how it makes you feel?
N/A