feat(sanity)!: support angular 21#70
Merged
Merged
Conversation
✅ Deploy Preview for limitless-angular-sanity-example canceled.
|
commit: |
osnoser1
changed the title
osnoser1
force-pushed
the
osnoser1/angular-21-support
branch
from
08f23b8 to
a451ca9
Compare
Update the active Angular compatibility window to Angular 19 through 21, refresh the Angular 21 workspace toolchain, update the compatibility matrix, and apply the Angular 21 SSR bootstrap context migration. BREAKING CHANGE: Angular 18 is no longer included in the @limitless-angular/sanity peer dependency range or required compatibility matrix. Use Angular 19, Angular 20, or Angular 21 with this package line.
osnoser1
force-pushed
the
osnoser1/angular-21-support
branch
from
a451ca9 to
95494b3
Compare
Closed
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
1 participant
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 the next supported window. No issue number.
Closes #
N/A
What is the new behavior?
@limitless-angular/sanitypeer range and compatibility matrix.effectsignal-write compatibility branch from Portable Text directives.Does this PR introduce a breaking change?
BREAKING CHANGE: Angular 18 is no longer in the supported peer range or required compatibility matrix. Applications using this package line should use Angular 19, Angular 20, or Angular 21. Older package-line compatibility remains documented in the README table.
Other information
Validation run locally:
CI=true pnpm install --frozen-lockfilenode --test tools/angular-compat/*.test.mjspnpm run compat:assertpnpm run compat:matrixpnpm run compat:packpnpm run compat:artifactpnpm run compat:test --angular 21pnpm run compat:release-paritypnpm turbo run build test --affectedpnpm run lintpnpm --filter @limitless-angular/sanity buildpnpm --filter @limitless-angular/sanity testpnpm --filter @limitless-angular/sanity lintgit diff --checkOfficial
ng update @angular/core --migrate-only --from 20.0.0 --to 21.0.0 --allow-dirtyhit the repo-local tsconfig path issue documented in the Angular compatibility skill. I inspected Angular 21'sadd-bootstrap-context-to-server-mainmigration bundle and applied the sameBootstrapContextserver bootstrap changes manually. The remaining Angular core v21 migration targets were audited and did not apply.Package-manager note: pnpm has
autoInstallPeersenabled, and Analog declares optional broad peer ranges for Nx and Angular DevKit build tooling. The root overrides pin those auto-installed optional peers to Angular-21-compatible versions so pnpm does not resolve stale Nx 20 / Angular DevKit 19 peers into the Angular 21 workspace graph.[Optional] What gif best describes this PR or how it makes you feel?
N/A