feat(sanity)!: add Angular 22 support - #74
Merged
Merged
Conversation
✅ Deploy Preview for limitless-angular-sanity-example ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
BREAKING CHANGE: Angular 19 is no longer supported.
osnoser1
force-pushed
the
osnoser1/angular-22-support
branch
from
June 17, 2026 02:19
76ba300 to
dd56f72
Compare
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
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 the active Angular support contract for @limitless-angular/sanity from Angular 19-21 to Angular 20-22.
Closes N/A
What is the new behavior?
Does this PR introduce a breaking change?
Angular 19 is no longer supported. Consumers should upgrade to Angular 20 or newer before taking this release.
Other information
Validation completed locally:
pnpm installpnpm --filter sanity-example exec node -vpnpm --filter analog-sanity-blog-example exec node -vpnpm --filter sanity-presentation-e2e-preview exec node -vpnpm --filter sanity-example exec ng update @angular/core --migrate-only --from 21.0.0 --to 22.0.0 --allow-dirtyfailed before changes with the known repo tsconfig path issue:Cannot read file '/tsconfig.base.json'.pnpm --filter analog-sanity-blog-example exec ng update @angular/core --migrate-only --from 21.0.0 --to 22.0.0 --allow-dirtyfailed with the same known tsconfig path issue.pnpm --filter sanity-presentation-e2e-preview exec ng update @angular/core --migrate-only --from 21.0.0 --to 22.0.0 --allow-dirtyfailed with the same known tsconfig path issue.pnpm --filter sanity-example exec ng update @angular/cli --migrate-only --from 21.0.0 --to 22.0.0 --allow-dirtypnpm --filter analog-sanity-blog-example exec ng update @angular/cli --migrate-only --from 21.0.0 --to 22.0.0 --allow-dirtypnpm --filter sanity-presentation-e2e-preview exec ng update @angular/cli --migrate-only --from 21.0.0 --to 22.0.0 --allow-dirtynode --test tools/angular-compat/*.test.mjspnpm run compat:assertpnpm run compat:matrixpnpm run compat:packpnpm run compat:artifactpnpm run compat:test --angular 22pnpm run compat:test --set angular-22-floorpnpm run buildpnpm run testpnpm run lintSANITY_E2E_PREVIEW_PORT=44200 SANITY_E2E_PREVIEW_URL=http://localhost:44200 SANITY_E2E_STUDIO_PORT=44333 SANITY_E2E_STUDIO_URL=http://localhost:44333 pnpm --filter sanity-presentation-e2e e2eThe failed core migration was manually audited. There are no
canMatchcallsites, strict template checking is already configured, and the matching Angular 22 hydration behavior migration was applied manually.[Optional] What gif best describes this PR or how it makes you feel?
N/A