feat(sanity): widen supported sanity dependency majors - #36
Merged
Merged
Conversation
✅ Deploy Preview for limitless-angular-sanity-example ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
Summary
@limitless-angular/sanityand helper entrypoints.@sanity/client,@sanity/image-url,@portabletext/toolkit,@portabletext/types, and@sanity/typeswithout dropping existing peer support.@sanity/comlinkand@sanity/visual-editingconstrained where compatibility checks showed newer majors need more work.@sanity/image-urlv1 and v2 can both be supported.Partial<Record<...>>, matching the runtime merge behavior and allowing sparse overrides with@portabletext/typesv4.Why
Angular 18/19 support needs validation against the supported Sanity dependency majors directly. The previous dependency ranges and local examples did not exercise the newest compatible Sanity peer versions, and Portable Text v4 exposed that our component override type was stricter than the renderer behavior.
Validation
pnpm --filter @limitless-angular/sanity lintpnpm --filter @limitless-angular/sanity testpnpm --filter @limitless-angular/sanity buildpnpm --filter @limitless-angular/angular-compat testpnpm --filter analog-sanity-blog-example buildpnpm --filter sanity-example buildpnpm turbo run e2e --filter=sanity-presentation-e2epnpm compatpnpm compat:release-paritypnpm turbo run e2e-studio --filter=sanity-presentation-e2epnpm turbo run e2e-real-studio --filter=sanity-presentation-e2eNote:
pnpm peers checkstill reports unrelated existing workspace peer issues outside this Sanity compatibility change.