chore: version packages - #1339
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
Contributor
📚 TypeDoc Generation Result✅ TypeDoc generated successfully!
The TypeDoc JSON file has been generated and validated. All documentation scripts completed successfully. |
Contributor
Coverage Report
File CoverageNo changed files found. |
squiggler-app
Bot
force-pushed
the
changeset-release/main
branch
from
September 22, 2026 15:52
4bde88d to
61e3610
Compare
squiggler-app
Bot
force-pushed
the
changeset-release/main
branch
from
September 23, 2026 12:36
61e3610 to
202dc72
Compare
rexxars
approved these changes
Sep 23, 2026
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@sanity/client@8.7.0
Minor Changes
abort underlying EventSource request when response fails validation (#1340) (ba3de6b)
add per-resource schema, query and projection registries (#1334) (b43e033)
SanitySchemasByResource,SanityQueriesByResourceandSanityProjectionsByResourcejoin the existingSanityQueriesregistry, following the same pattern: a global interface that the interface exported from@sanity/clientinherits from, so a generated file can register either way and does not depend on module resolution.Each is keyed by a resource, using the same string the App SDK already uses for its runtime cache,
projectId.datasetfor a dataset. This is what lets two datasets whose schemas disagree register different result types for the same query text, which the flatSanityQueriesregistry cannot express. Projections add a document-type level, because a projection resolves against whichever document the caller's handle names.All three are empty by default and nothing in the client reads them yet.
client.fetchandClientReturnare unchanged, and keep resolving through the flat registry. They exist for consumers that do resource-aware lookups themselves, starting with the App SDK's hooks.Patch Changes
Note
Low Risk
Release-only diff in this PR; shipped behavior is additive typing plus EventSource cleanup and RN retries, with no change to default fetch typing.
Overview
This Changesets release PR cuts
@sanity/client8.7.0: it bumpspackage.json, adds the 8.7.0 section toCHANGELOG.md, and removes the consumed changeset files so npm can publish.The release bundles three already-merged changes:
EventSource: live/listen paths now abort the underlying EventSource when the response fails validation, instead of leaving the connection open.
Type registries (minor): new global
SanitySchemasByResource,SanityQueriesByResource, andSanityProjectionsByResourceinterfaces, keyed by resource (e.g.projectId.dataset), for per-dataset type registration. They are empty by default;client.fetchandClientReturnstill use the flatSanityQueriesregistry.React Native (patch): HTTP requests retry in React Native where they previously did not.
Reviewed by Cursor Bugbot for commit 202dc72. Bugbot is set up for automated code reviews on this repo. Configure here.