Version Packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish 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

@urql/exchange-graphcache@9.0.1

Patch Changes

• ⚠️ Fix relayPagination merging pages in the order they were written to the cache rather than in their cursor order. When multiple pages were requested concurrently and a later page's response was written before an earlier one's, the combined edges/nodes could transiently end up in the wrong order. Pages are now reordered along their cursor chain (via after/endCursor and before/startCursor) before being concatenated, while pages without a known predecessor keep their original order
  Submitted by @moriyuu (See #3877)
• Remove the invalid exports field from the generated subpath package.json files (e.g. @urql/exchange-graphcache/extras, @urql/exchange-graphcache/default-storage, @urql/core/internal, @urql/next/rsc). These targets pointed at the parent dist/ directory (../dist/...), which violates the Node.js package-exports spec requirement that every exports target begin with ./. Metro (Expo 53 / React Native 0.79) validates this and logged a warning for every affected package. Subpath resolution continues to work: exports-aware bundlers resolve through the root package.json, while legacy resolution relies on the main/module/types fields that remain in place
  Submitted by @JoviDeCroock (See #3886)
• Updated dependencies (See #3879, #3881, #3885, and #3886)
  • @urql/core@6.0.2

@urql/core@6.0.2

Patch Changes

• Prevent mapExchange from forwarding async-mapped operations after their teardown has already been received
  Submitted by @JoviDeCroock (See #3879)
• Unwrap the payload property in makeResult so that the first incremental/multipart response is parsed correctly. Previously, transports that wrap each result in a payload property (e.g. Apollo Federation's multipart subscriptions) would have their first response dropped as "No Content", while subsequent responses were handled correctly by mergeResultPatch
  Submitted by @JoviDeCroock (See #3881)
• Emit terminal subscription results before ending completed subscriptions, preventing teardown races from dropping GraphQL errors
  Submitted by @JoviDeCroock (See #3885)
• Remove the invalid exports field from the generated subpath package.json files (e.g. @urql/exchange-graphcache/extras, @urql/exchange-graphcache/default-storage, @urql/core/internal, @urql/next/rsc). These targets pointed at the parent dist/ directory (../dist/...), which violates the Node.js package-exports spec requirement that every exports target begin with ./. Metro (Expo 53 / React Native 0.79) validates this and logged a warning for every affected package. Subpath resolution continues to work: exports-aware bundlers resolve through the root package.json, while legacy resolution relies on the main/module/types fields that remain in place
  Submitted by @JoviDeCroock (See #3886)

@urql/next@2.0.1

Patch Changes

• Remove the invalid exports field from the generated subpath package.json files (e.g. @urql/exchange-graphcache/extras, @urql/exchange-graphcache/default-storage, @urql/core/internal, @urql/next/rsc). These targets pointed at the parent dist/ directory (../dist/...), which violates the Node.js package-exports spec requirement that every exports target begin with ./. Metro (Expo 53 / React Native 0.79) validates this and logged a warning for every affected package. Subpath resolution continues to work: exports-aware bundlers resolve through the root package.json, while legacy resolution relies on the main/module/types fields that remain in place
  Submitted by @JoviDeCroock (See #3886)

urql@5.0.3

Patch Changes

• ⚠️ Fix React Suspense error-boundary resets reusing cached error results instead of retrying the query
  Submitted by @JoviDeCroock (See #3887)
• Updated dependencies (See #3879, #3881, #3885, and #3886)
  • @urql/core@6.0.2

@urql/vue@2.1.1

Patch Changes

• Stop useQuery from re-executing (and hitting the network) during SSR hydration when it's awaited for Suspense. Awaiting the query subscribed to the operation a second time, which re-dispatched it after the ssrExchange result had already been consumed, triggering a redundant network request even with staleWhileRevalidate: false. The awaited promise now resolves with the already-settled result instead of re-subscribing
  Submitted by @JoviDeCroock (See #3884)
• ⚠️ Fix await useQuery() in Vue to wait on the composable's existing reactive state instead of creating an additional query source subscription
  Submitted by @JoviDeCroock (See #3890)
• Updated dependencies (See #3879, #3881, #3885, and #3886)
  • @urql/core@6.0.2

[cloudflare-workers-and-pages]

Deploying urql with    Cloudflare Pages

Latest commit:	7d29364
Status:	✅  Deploy successful!
Preview URL:	https://8b3b580b.urql.pages.dev
Branch Preview URL:	https://changeset-release-main.urql.pages.dev

View logs