Version Packages

[urql-ci]

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

@urql/[email protected]

Minor Changes

• Fixed typing of OptimisticMutationResolver, by @taneba (See #1765)

Patch Changes

• Type the relayPagination and simplePagination helpers return value as Resolver<any, any, any> as there's no way to match them consistently to either generated or non-generated resolver types anymore, by @kitten (See #1778)
• Updated dependencies (See #1776 and #1755)
  • @urql/[email protected]

@urql/[email protected]

Minor Changes

• Improve granularity of operationStore updates when query, variables, and context are changed. This also adds an operationStore(...).reexecute() method, which optionally accepts a new context value and forces an update on the store, so that a query may reexecute, by @kitten (See #1780)

Patch Changes

• Loosen subscription(...) type further to allow any operationStore input, regardless of the Result produced, by @kitten (See #1779)
• Updated dependencies (See #1776 and #1755)
  • @urql/[email protected]

@urql/[email protected]

Patch Changes

• Optimize for minification by avoiding direct eval call, by @nderscore (See #1744)
• Updated dependencies (See #1776 and #1755)
  • @urql/[email protected]

@urql/[email protected]

Patch Changes

• Do not set the TTL unless cache outcome is "miss". Previously we set the TTL on cache "miss" if it was the first time an operation returned a result, now the TTL is only set on cache miss results. This allows the request policy exchange to work when using persisted caching, by @Mookiies (See #1742)
• Updated dependencies (See #1776 and #1755)
  • @urql/[email protected]

@urql/[email protected]

Patch Changes

• Prevent ssrExchange().restoreData() from adding results to the exchange that have already been invalidated. This may happen when restoreData() is called repeatedly, e.g. per page. When a prior run has already invalidated an SSR result then the result is 'migrated' to the user's cacheExchange, which means that restoreData() should never attempt to re-add it again, by @kitten (See #1776)
• ⚠️ Fix accidental change in passive stale: true, where a cache-first operation issued by Graphcache wouldn't yield an affected query and update its result to reflect the loading state with stale: true. This is a regression from v2.1.0 and mostly becomes unexpected when cache.invalidate(...) is used, by @kitten (See #1755)

[email protected]

Patch Changes

• ⚠️ Fix resetUrqlClient not resetting the SSR cache itself and instead restoring data when all data related to this Client and session should've been deleted, by @Biboswan (See #1715)

@urql/[email protected]

Patch Changes

• Refactor useQuery implementation to utilise the single-source implementation of @urql/[email protected]. This should improve the stability of promisified useQuery() calls and prevent operations from not being issued in some edge cases, by @kitten (See #1758)
• Updated dependencies (See #1776 and #1755)
  • @urql/[email protected]