···11----
22-'next-urql': patch
33----
44-55-Prevent serialization of the `Client` for `withUrqlClient` even if the target component doesn't have a `getInitialProps` method. Before this caused the client to not be initialised correctly on the client-side.
-5
.changeset/rich-eels-shop.md
···11----
22-'@urql/exchange-graphcache': patch
33----
44-55-Add warning for queries that traverse an Operation Root Type (Mutation / Subscription types occuring in a query result)
-39
.changeset/strange-donuts-listen.md
···11----
22-'@urql/svelte': minor
33----
44-55-Refactor all operations to allow for more use-cases which preserve state and allow all modes of Svelte to be applied to urql.
66-77-```
88-// Standard Usage:
99-mutate({ query, variables })()
1010-1111-// Subscribable Usage:
1212-$: result = mutate({ query, variables });
1313-1414-// Curried Usage
1515-const executeMutation = mutate({ query, variables });
1616-const onClick = () => executeMutation();
1717-1818-// Curried Usage with overrides
1919-const executeMutation = mutate({ query });
2020-const onClick = () => await executeMutation({ variables });
2121-2222-// Subscribable Usage (as before):
2323-$: result = query({ query: TestQuery, variables });
2424-2525-// Subscribable Usage which preserves state over time:
2626-const testQuery = query({ query: TestQuery });
2727-// - this preserves the state even when the variables change!
2828-$: result = testQuery({ variables });
2929-3030-// Promise-based callback usage:
3131-const testQuery = query({ query: TestQuery });
3232-const doQuery = async () => await testQuery;
3333-3434-// Promise-based usage updates the subscribables!
3535-const testQuery = query({ query: TestQuery });
3636-const doQuery = async () => await testQuery;
3737-// - doQuery will also update this result
3838-$: result = query({ query: TestQuery, variables });
3939-```
-5
.changeset/strong-games-scream.md
···11----
22-'@urql/core': patch
33----
44-55-Fix timing for out-of-band `client.reexecuteOperation` calls. This would surface in asynchronous caching scenarios, where no result would be delivered by the cache synchronously, while it still calls `client.reexecuteOperation` for e.g. a `network-only` request, which happens for `cache-and-network`. This issue becomes especially obvious in highly synchronous frameworks like Svelte.
-5
.changeset/thick-bees-decide.md
···11----
22-'@urql/exchange-graphcache': patch
33----
44-55-Fix storage implementation not preserving deleted values correctly or erroneously checking optimistically written entries for changes. This is fixed by adding a new default serializer to the `@urql/exchange-graphcache/default-storage` implementation, which will be incompatible with the old one.
···11# @urql/exchange-graphcache
2233+## 3.0.1
44+55+### Patch Changes
66+77+- Add warning for queries that traverse an Operation Root Type (Mutation / Subscription types occuring in a query result), by [@kitten](https://github.com/kitten) (See [#859](https://github.com/FormidableLabs/urql/pull/859))
88+- ⚠️ Fix storage implementation not preserving deleted values correctly or erroneously checking optimistically written entries for changes. This is fixed by adding a new default serializer to the `@urql/exchange-graphcache/default-storage` implementation, which will be incompatible with the old one, by [@kitten](https://github.com/kitten) (See [#866](https://github.com/FormidableLabs/urql/pull/866))
99+- Replace unnecessary `scheduleTask` polyfill with inline `Promise.resolve().then(fn)` calls, by [@kitten](https://github.com/kitten) (See [#861](https://github.com/FormidableLabs/urql/pull/861))
1010+- Updated dependencies (See [#860](https://github.com/FormidableLabs/urql/pull/860) and [#861](https://github.com/FormidableLabs/urql/pull/861))
1111+ - @urql/core@1.12.1
1212+313## 3.0.0
414515This major release comes with a couple of fixes and new **experimental offline support**, which
···11# @urql/core
2233+## 1.12.1
44+55+### Patch Changes
66+77+- ⚠️ Fix timing for out-of-band `client.reexecuteOperation` calls. This would surface in asynchronous caching scenarios, where no result would be delivered by the cache synchronously, while it still calls `client.reexecuteOperation` for e.g. a `network-only` request, which happens for `cache-and-network`. This issue becomes especially obvious in highly synchronous frameworks like Svelte, by [@kitten](https://github.com/kitten) (See [#860](https://github.com/FormidableLabs/urql/pull/860))
88+- Replace unnecessary `scheduleTask` polyfill with inline `Promise.resolve().then(fn)` calls, by [@kitten](https://github.com/kitten) (See [#861](https://github.com/FormidableLabs/urql/pull/861))
99+310## 1.12.0
411512As always, please ensure that you deduplicate `@urql/core` when upgrading. Additionally
+1-1
packages/core/package.json
···11{
22 "name": "@urql/core",
33- "version": "1.12.0",
33+ "version": "1.12.1",
44 "description": "The shared core for the highly customizable and versatile GraphQL client",
55 "sideEffects": false,
66 "homepage": "https://formidable.com/open-source/urql/docs/",
+13-4
packages/next-urql/CHANGELOG.md
···11# Changelog
2233+## 1.0.1
44+55+### Patch Changes
66+77+- Prevent serialization of the `Client` for `withUrqlClient` even if the target component doesn't have a `getInitialProps` method. Before this caused the client to not be initialised correctly on the client-side, by [@JoviDeCroock](https://github.com/JoviDeCroock) (See [#857](https://github.com/FormidableLabs/urql/pull/857))
88+39## 1.0.0
410511To migrate to the new version, you will now have to pass a single function argument, instead
···1723To look like the following:
18241925```js
2020-export default withUrqlClient((ssrExchange, ctx) => ({
2121- url: '',
2222- exchanges: [dedupExchange, cacheExchange, ssrExchange, fetchExchange]
2323-}), { ssr: true });
2626+export default withUrqlClient(
2727+ (ssrExchange, ctx) => ({
2828+ url: '',
2929+ exchanges: [dedupExchange, cacheExchange, ssrExchange, fetchExchange],
3030+ }),
3131+ { ssr: true }
3232+);
2433```
25342635The second argument may now be used to pass `{ ssr: true }` explicitly, when you are
+1-1
packages/next-urql/package.json
···11{
22 "name": "next-urql",
33- "version": "1.0.0",
33+ "version": "1.0.1",
44 "description": "Convenience wrappers for using urql with NextJS.",
55 "sideEffects": false,
66 "homepage": "https://formidable.com/open-source/urql/docs/",
+37
packages/svelte-urql/CHANGELOG.md
···11# @urql/svelte
2233+## 0.3.0
44+55+### Minor Changes
66+77+- Refactor all operations to allow for more use-cases which preserve state and allow all modes of Svelte to be applied to urql.
88+ ```
99+ // Standard Usage:
1010+ mutate({ query, variables })()
1111+ // Subscribable Usage:
1212+ $: result = mutate({ query, variables });
1313+ // Curried Usage
1414+ const executeMutation = mutate({ query, variables });
1515+ const onClick = () => executeMutation();
1616+ // Curried Usage with overrides
1717+ const executeMutation = mutate({ query });
1818+ const onClick = () => await executeMutation({ variables });
1919+ // Subscribable Usage (as before):
2020+ $: result = query({ query: TestQuery, variables });
2121+ // Subscribable Usage which preserves state over time:
2222+ const testQuery = query({ query: TestQuery });
2323+ // - this preserves the state even when the variables change!
2424+ $: result = testQuery({ variables });
2525+ // Promise-based callback usage:
2626+ const testQuery = query({ query: TestQuery });
2727+ const doQuery = async () => await testQuery;
2828+ // Promise-based usage updates the subscribables!
2929+ const testQuery = query({ query: TestQuery });
3030+ const doQuery = async () => await testQuery;
3131+ // - doQuery will also update this result
3232+ $: result = query({ query: TestQuery, variables });
3333+ ```
3434+3535+### Patch Changes
3636+3737+- Updated dependencies (See [#860](https://github.com/FormidableLabs/urql/pull/860) and [#861](https://github.com/FormidableLabs/urql/pull/861))
3838+ - @urql/core@1.12.1
3939+340## 0.2.4
441542### Patch Changes