iamstarkov / topics-manager

Serverless App to manage GitHub repos' topics
https://topics-manager.now.sh
6 stars 0 forks source link

Update dependency urql to v1.11.6 #162

Closed renovate[bot] closed 3 years ago

renovate[bot] commented 4 years ago

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
urql (source) 1.6.1 -> 1.11.6 age adoption passing confidence

Release Notes

FormidableLabs/urql ### [`v1.11.6`](https://togithub.com/FormidableLabs/urql/releases/urql@1.11.6) [Compare Source](https://togithub.com/FormidableLabs/urql/compare/urql@1.11.5...urql@1.11.6) ##### Patch Changes - ⚠️ Fix edge cases related to Suspense triggering on an update in Concurrent Mode. Previously it was possible for stale state to be preserved across the Suspense update instead of the new state showing up. This has been fixed by preventing the suspending query source from closing prematurely, by [@​kitten](https://togithub.com/kitten) (See [#​1308](https://togithub.com/FormidableLabs/urql/pull/1308)) ### [`v1.11.5`](https://togithub.com/FormidableLabs/urql/releases/urql@1.11.5) [Compare Source](https://togithub.com/FormidableLabs/urql/compare/urql@1.11.4...urql@1.11.5) ##### Patch Changes - ⚠️ Fix Suspense when results share data, this would return partial results for graphCache and not update to the eventual data, by [@​JoviDeCroock](https://togithub.com/JoviDeCroock) (See [#​1282](https://togithub.com/FormidableLabs/urql/pull/1282)) ### [`v1.11.4`](https://togithub.com/FormidableLabs/urql/releases/urql@1.11.4) [Compare Source](https://togithub.com/FormidableLabs/urql/compare/urql@1.11.3...urql@1.11.4) ##### Patch Changes - Add a built-in `gql` tag function helper to `@urql/core`. This behaves similarly to `graphql-tag` but only warns about *locally* duplicated fragment names rather than globally. It also primes `@urql/core`'s key cache with the parsed `DocumentNode`, by [@​kitten](https://togithub.com/kitten) (See [#​1187](https://togithub.com/FormidableLabs/urql/pull/1187)) - Add `suspense: false` to options when `executeQuery` is called explicitly, by [@​kitten](https://togithub.com/kitten) (See [#​1181](https://togithub.com/FormidableLabs/urql/pull/1181)) - Updated dependencies (See [#​1187](https://togithub.com/FormidableLabs/urql/pull/1187), [#​1186](https://togithub.com/FormidableLabs/urql/pull/1186), and [#​1186](https://togithub.com/FormidableLabs/urql/pull/1186)) - [@​urql/core](https://togithub.com/urql/core)[@​1](https://togithub.com/1).16.0 ### [`v1.11.3`](https://togithub.com/FormidableLabs/urql/releases/urql@1.11.3) [Compare Source](https://togithub.com/FormidableLabs/urql/compare/urql@1.11.2...urql@1.11.3) ##### Patch Changes - ⚠️ Fix in edge-case in client-side React Suspense, where after suspending due to an update a new state value is given to `useSource` in a render update. This was previously then causing us to subscribe to an outdated source in `useEffect` since the updated source would be ignored by the time we reach `useEffect` in `useSource`, by [@​kitten](https://togithub.com/kitten) (See [#​1157](https://togithub.com/FormidableLabs/urql/pull/1157)) ### [`v1.11.2`](https://togithub.com/FormidableLabs/urql/releases/urql@1.11.2) [Compare Source](https://togithub.com/FormidableLabs/urql/compare/urql@1.11.1...urql@1.11.2) ##### Patch Changes - ⚠️ Fix regression in client-side Suspense behaviour. This has been fixed in `urql@1.11.0` and `@urql/preact@1.4.0` but regressed in the patches afterwards that were aimed at fixing server-side Suspense, by [@​kitten](https://togithub.com/kitten) (See [#​1142](https://togithub.com/FormidableLabs/urql/pull/1142)) ### [`v1.11.1`](https://togithub.com/FormidableLabs/urql/releases/urql@1.11.1) [Compare Source](https://togithub.com/FormidableLabs/urql/compare/urql@1.11.0...urql@1.11.1) ##### Patch Changes - ⚠️ Fix server-side rendering by disabling the new Suspense cache on the server-side and clear it for prepasses, by [@​JoviDeCroock](https://togithub.com/JoviDeCroock) (See [#​1138](https://togithub.com/FormidableLabs/urql/pull/1138)) - Updated dependencies (See [#​1135](https://togithub.com/FormidableLabs/urql/pull/1135)) - [@​urql/core](https://togithub.com/urql/core)[@​1](https://togithub.com/1).15.1 ### [`v1.11.0`](https://togithub.com/FormidableLabs/urql/releases/urql@1.11.0) [Compare Source](https://togithub.com/FormidableLabs/urql/compare/urql@1.10.3...urql@1.11.0) ##### Minor Changes - Improve the Suspense implementation, which fixes edge-cases when Suspense is used with subscriptions, partially disabled, or *used on the client-side*. It has now been ensured that client-side suspense functions without the deprecated `suspenseExchange` and uncached results are loaded consistently. As part of this work, the `Client` itself does now never throw Suspense promises anymore, which is functionality that either way has no place outside of the React/Preact bindings, by [@​kitten](https://togithub.com/kitten) (See [#​1123](https://togithub.com/FormidableLabs/urql/pull/1123)) ##### Patch Changes - Add support for `TypedDocumentNode` to infer the type of the `OperationResult` and `Operation` for all methods, functions, and hooks that either directly or indirectly accept a `DocumentNode`. See [`graphql-typed-document-node` and the corresponding blog post for more information.](https://togithub.com/dotansimha/graphql-typed-document-node), by [@​kitten](https://togithub.com/kitten) (See [#​1113](https://togithub.com/FormidableLabs/urql/pull/1113)) - Refactor `useSource` hooks which powers `useQuery` and `useSubscription` to improve various edge case behaviour. This will not change the behaviour of these hooks dramatically but avoid unnecessary state updates when any updates are obviously equivalent and the hook will furthermore improve continuation from mount to effects, which will fix cases where the state between the mounting and effect phase may slightly change, by [@​kitten](https://togithub.com/kitten) (See [#​1104](https://togithub.com/FormidableLabs/urql/pull/1104)) - Updated dependencies (See [#​1119](https://togithub.com/FormidableLabs/urql/pull/1119), [#​1113](https://togithub.com/FormidableLabs/urql/pull/1113), [#​1104](https://togithub.com/FormidableLabs/urql/pull/1104), and [#​1123](https://togithub.com/FormidableLabs/urql/pull/1123)) - [@​urql/core](https://togithub.com/urql/core)[@​1](https://togithub.com/1).15.0 ### [`v1.10.3`](https://togithub.com/FormidableLabs/urql/releases/urql@1.10.3) [Compare Source](https://togithub.com/FormidableLabs/urql/compare/urql@1.10.2...urql@1.10.3) ##### Patch Changes - ⚠️ Fix the production build overwriting the development build. Specifically in the previous release we mistakenly replaced all development bundles with production bundles. This doesn't have any direct influence on how these packages work, but prevented development warnings from being logged or full errors from being thrown, by [@​kitten](https://togithub.com/kitten) (See [#​1097](https://togithub.com/FormidableLabs/urql/pull/1097)) - Updated dependencies (See [#​1097](https://togithub.com/FormidableLabs/urql/pull/1097)) - [@​urql/core](https://togithub.com/urql/core)[@​1](https://togithub.com/1).14.1 ### [`v1.10.2`](https://togithub.com/FormidableLabs/urql/releases/urql@1.10.2) [Compare Source](https://togithub.com/FormidableLabs/urql/compare/urql@1.10.1...urql@1.10.2) ##### Patch Changes - Deprecate the `Operation.operationName` property in favor of `Operation.kind`. This name was previously confusing as `operationName` was effectively referring to two different things. You can safely upgrade to this new version, however to mute all deprecation warnings you will have to **upgrade** all `urql` packages you use. If you have custom exchanges that spread operations, please use [the new `makeOperation` helper function](https://formidable.com/open-source/urql/docs/api/core/#makeoperation) instead, by [@​bkonkle](https://togithub.com/bkonkle) (See [#​1045](https://togithub.com/FormidableLabs/urql/pull/1045)) - Updated dependencies (See [#​1094](https://togithub.com/FormidableLabs/urql/pull/1094) and [#​1045](https://togithub.com/FormidableLabs/urql/pull/1045)) - [@​urql/core](https://togithub.com/urql/core)[@​1](https://togithub.com/1).14.0 ### [`v1.10.1`](https://togithub.com/FormidableLabs/urql/releases/urql@1.10.1) [Compare Source](https://togithub.com/FormidableLabs/urql/compare/urql@1.10.0...urql@1.10.1) ##### Patch Changes - ⚠️ Fix React Fast Refresh being broken due to an invalid effect, by [@​JoviDeCroock](https://togithub.com/JoviDeCroock) (See [#​969](https://togithub.com/FormidableLabs/urql/pull/969)) ### [`v1.10.0`](https://togithub.com/FormidableLabs/urql/releases/urql@1.10.0) [Compare Source](https://togithub.com/FormidableLabs/urql/compare/urql@1.9.8...urql@1.10.0) ##### Minor Changes - Add the operation to the query, mutation and subscription result, by [@​JoviDeCroock](https://togithub.com/JoviDeCroock) (See [#​924](https://togithub.com/FormidableLabs/urql/pull/924)) ##### Patch Changes - Update hooks to be exported functions rather than exported block-scoped variables to provide TypeScript consumers with better access to their signature, by [@​dotansimha](https://togithub.com/dotansimha) (See [#​904](https://togithub.com/FormidableLabs/urql/pull/904)) - Updated dependencies (See [#​911](https://togithub.com/FormidableLabs/urql/pull/911) and [#​908](https://togithub.com/FormidableLabs/urql/pull/908)) - [@​urql/core](https://togithub.com/urql/core)[@​1](https://togithub.com/1).12.3 ### [`v1.9.8`](https://togithub.com/FormidableLabs/urql/releases/urql@1.9.8) [Compare Source](https://togithub.com/FormidableLabs/urql/compare/urql@1.9.7...urql@1.9.8) ##### Patch Changes - Upgrade to a minimum version of wonka@^4.0.14 to work around issues with React Native's minification builds, which use uglify-es and could lead to broken bundles, by [@​kitten](https://togithub.com/kitten) (See [#​842](https://togithub.com/FormidableLabs/urql/pull/842)) - Updated dependencies (See [#​838](https://togithub.com/FormidableLabs/urql/pull/838) and [#​842](https://togithub.com/FormidableLabs/urql/pull/842)) - [@​urql/core](https://togithub.com/urql/core)[@​1](https://togithub.com/1).12.0 ### [`v1.9.7`](https://togithub.com/FormidableLabs/urql/releases/urql@1.9.7) [Compare Source](https://togithub.com/FormidableLabs/urql/compare/urql@1.9.6...urql@1.9.7) ##### Patch Changes - Bump [@​urql/core](https://togithub.com/urql/core) to ensure exchanges have dispatchDebug, this could formerly result in a crash, by [@​JoviDeCroock](https://togithub.com/JoviDeCroock) (See [#​726](https://togithub.com/FormidableLabs/urql/pull/726)) ### [`v1.9.6`](https://togithub.com/FormidableLabs/urql/releases/urql@1.9.6) [Compare Source](https://togithub.com/FormidableLabs/urql/compare/urql@1.9.5...urql@1.9.6) ##### Patch Changes - Add graphql@^15.0.0 to peer dependency range, by [@​kitten](https://togithub.com/kitten) (See [#​688](https://togithub.com/FormidableLabs/urql/pull/688)) - Forcefully bump [@​urql/core](https://togithub.com/urql/core) package in all bindings and in [@​urql/exchange-graphcache](https://togithub.com/urql/exchange-graphcache). We're aware that in some cases users may not have upgraded to [@​urql/core](https://togithub.com/urql/core), even though that's within the typical patch range. Since the latest [@​urql/core](https://togithub.com/urql/core) version contains a patch that is required for `cache-and-network` to work, we're pushing another patch that now forcefully bumps everyone to the new version that includes this fix, by [@​kitten](https://togithub.com/kitten) (See [#​684](https://togithub.com/FormidableLabs/urql/pull/684)) - Updated dependencies (See [#​688](https://togithub.com/FormidableLabs/urql/pull/688) and [#​678](https://togithub.com/FormidableLabs/urql/pull/678)) - [@​urql/core](https://togithub.com/urql/core)[@​1](https://togithub.com/1).10.8 ### [`v1.9.5`](https://togithub.com/FormidableLabs/urql/releases/urql@1.9.5) [Compare Source](https://togithub.com/FormidableLabs/urql/compare/urql@1.9.4...urql@1.9.5) ##### Patch Changes - Avoid setting state on an unmounted component when useMutation is used, by [@​JoviDeCroock](https://togithub.com/JoviDeCroock) (See [#​656](https://togithub.com/FormidableLabs/urql/pull/656)) - Updated dependencies (See [#​658](https://togithub.com/FormidableLabs/urql/pull/658) and [#​650](https://togithub.com/FormidableLabs/urql/pull/650)) - [@​urql/core](https://togithub.com/urql/core)[@​1](https://togithub.com/1).10.5 ### [`v1.9.4`](https://togithub.com/FormidableLabs/urql/releases/urql@1.9.4) [Compare Source](https://togithub.com/FormidableLabs/urql/compare/urql@1.9.3...urql@1.9.4) ##### Patch Changes - ⚠️ Fix bundling for packages depending on React, as it doesn't have native ESM bundles, by [@​kitten](https://togithub.com/kitten) (See [#​646](https://togithub.com/FormidableLabs/urql/pull/646)) ### [`v1.9.3`](https://togithub.com/FormidableLabs/urql/releases/urql@1.9.3) [Compare Source](https://togithub.com/FormidableLabs/urql/compare/urql@1.9.2...urql@1.9.3) ##### Patch Changes - ⚠️ Fix node resolution when using Webpack, which experiences a bug where it only resolves `package.json:main` instead of `module` when an `.mjs` file imports a package, by [@​JoviDeCroock](https://togithub.com/JoviDeCroock) (See [#​642](https://togithub.com/FormidableLabs/urql/pull/642)) - Updated dependencies (See [#​642](https://togithub.com/FormidableLabs/urql/pull/642)) - [@​urql/core](https://togithub.com/urql/core)[@​1](https://togithub.com/1).10.4 ### [`v1.9.2`](https://togithub.com/FormidableLabs/urql/releases/urql@1.9.2) [Compare Source](https://togithub.com/FormidableLabs/urql/compare/urql@1.9.1...urql@1.9.2) ##### Patch Changes - ⚠️ Fix Node.js Module support for v13 (experimental-modules) and v14. If your bundler doesn't support `.mjs` files and fails to resolve the new version, please double check your configuration for Webpack, or similar tools, by [@​JoviDeCroock](https://togithub.com/JoviDeCroock) (See [#​637](https://togithub.com/FormidableLabs/urql/pull/637)) - Updated dependencies (See [#​637](https://togithub.com/FormidableLabs/urql/pull/637)) - [@​urql/core](https://togithub.com/urql/core)[@​1](https://togithub.com/1).10.3 ### [`v1.9.1`](https://togithub.com/FormidableLabs/urql/releases/urql@1.9.1) [Compare Source](https://togithub.com/FormidableLabs/urql/compare/urql@1.9.0...urql@1.9.1) - Bumps the `@urql/core` dependency minor version to ^1.10.1 for React, Preact and Svelte, by [@​JoviDeCroock](https://togithub.com/JoviDeCroock) (See [#​623](https://togithub.com/FormidableLabs/urql/pull/623)) - Avoid React v16.13.0's "Warning: Cannot update a component" by preventing cross-hook updates during render or initial mount, by [@​kitten](https://togithub.com/kitten) (See [#​630](https://togithub.com/FormidableLabs/urql/pull/630)) - Updated dependencies (See [#​621](https://togithub.com/FormidableLabs/urql/pull/621)) - [@​urql/core](https://togithub.com/urql/core)[@​1](https://togithub.com/1).10.2 ### [`v1.9.0`](https://togithub.com/FormidableLabs/urql/releases/urql@1.9.0) [Compare Source](https://togithub.com/FormidableLabs/urql/compare/v1.8.2...urql@1.9.0) ##### Patch Changes - ⚠️ Fix more concurrent-mode and strict-mode edge cases and bugs by switching to useSubscription. (See [#​514](https://togithub.com/FormidableLabs/urql/pull/514)) - ⚠️ Fix client-side suspense support (as minimally as possible) by altering the useBehaviourSubject behaviour. (See [#​512](https://togithub.com/FormidableLabs/urql/pull/521)) - Updated dependencies (See [#​533](https://togithub.com/FormidableLabs/urql/pull/533), [#​519](https://togithub.com/FormidableLabs/urql/pull/519), [#​515](https://togithub.com/FormidableLabs/urql/pull/515), [#​512](https://togithub.com/FormidableLabs/urql/pull/512), and [#​518](https://togithub.com/FormidableLabs/urql/pull/518)) - [@​urql/core](https://togithub.com/urql/core)[@​1](https://togithub.com/1).9.0 ### [`v1.8.2`](https://togithub.com/FormidableLabs/urql/releases/v1.8.2) [Compare Source](https://togithub.com/FormidableLabs/urql/compare/v1.8.1...v1.8.2) This patch fixes client-side suspense. While we wouldn't recommend its use anymore, since suspense lends itself to prerendering instead of a loading primitive, we'd like to ensure that suspense-mode works as expected in `urql`. Also, as mentioned in `v1.8.0`'s notes, please ensure that `urql` upgrades to use `wonka@^4.0.7` to avoid any issues. If your bundler or packager uses a lower version with `urql`, you will see runtime errors. - Clean up unnecessary `useMemo` for `useCallback` in hooks (see [#​504](https://togithub.com/FormidableLabs/urql/pull/504)) - Fix synchronous, client-side suspense and simplify `toSuspenseSource` helper (see [#​506](https://togithub.com/FormidableLabs/urql/pull/506)) ### [`v1.8.1`](https://togithub.com/FormidableLabs/urql/releases/v1.8.1) [Compare Source](https://togithub.com/FormidableLabs/urql/compare/v1.8.0...v1.8.1) This patch fixes `urql` relying on a quirk in older versions of `wonka` where shared sources wouldn't cascade cancellations, which they now do. This meant that when an app goes from some queries/subscriptions to having none at all, the exchange pipeline would be stopped completely. - Fix exchange pipeline stalling when all queries end (see [#​503](https://togithub.com/FormidableLabs/urql/pull/503)) ### [`v1.8.0`](https://togithub.com/FormidableLabs/urql/releases/v1.8.0) [Compare Source](https://togithub.com/FormidableLabs/urql/compare/v1.7.0...v1.8.0) This release doesn't change any major feature aspects, but comes with bugfixes to our suspense and concurrent-mode handling. Due to an upgrade to `wonka@^4.0.0` this is a minor version though. In [v1.6.0](https://togithub.com/FormidableLabs/urql/blob/master/CHANGELOG.md#v160) we believed to have solved all issues related to suspense and concurrent mode. However there were still some remaining cases where concurrent mode behaved incorrectly. With the new `useOperator` hook in [`react-wonka@2.0.0`](https://togithub.com/kitten/react-wonka) we believe to have now fixed all issues. The initial mount of `useQuery` and `useSubscription` will now synchronously reflect whatever `urql` returns, most of the times those will be cached results. Afterwards all subsequent updates and fetches will be scheduled cooperatively with React on an effect. If you're using `wonka` for an exchange with `urql` you may want to upgrade to `wonka@^4.0.5` soon. You can still use the older `v3.2.2` which will work with the new version (even in the same bundle), unless you're making use of its `subscribe`, `make`, or `makeSubject` exports. [A migration guide can be found in the `wonka` docs.](https://wonka.kitten.sh/migration) - Support concurrent mode with all edge cases fully (see [#​496](https://togithub.com/FormidableLabs/urql/pull/496)) - Move to `react-wonka@2.0.0` with the prior fix in [#​496](https://togithub.com/FormidableLabs/urql/issues/496) (see [#​499](https://togithub.com/FormidableLabs/urql/pull/499)) ### [`v1.7.0`](https://togithub.com/FormidableLabs/urql/releases/v1.7.0) [Compare Source](https://togithub.com/FormidableLabs/urql/compare/v1.6.3...v1.7.0) This release splits our main package into two entrypoints. Importing from `urql` remains unchanged, but internally this entrypoint uses `urql/core`, which doesn't contain any React-related code. If you're building framework-agnostic libraries or apps without React, you can now use `urql/core` directly. - Fix `originalError` on `GraphQLError` instances (see [#​470](https://togithub.com/FormidableLabs/urql/pull/470)) - Fix `stringifyVariables` not using `.toJSON()` which prevented Dates from being stringified, by [@​BjoernRave](https://togithub.com/BjoernRave) (see [#​485](https://togithub.com/FormidableLabs/urql/pull/485)) - Expose `urql/core` without any React code included (see [#​424](https://togithub.com/FormidableLabs/urql/pull/424)) ### [`v1.6.3`](https://togithub.com/FormidableLabs/urql/releases/v1.6.3) [Compare Source](https://togithub.com/FormidableLabs/urql/compare/v1.6.2...v1.6.3) - Fix suspense-mode being erroneously activated when using `client.query()` (see [#​466](https://togithub.com/FormidableLabs/urql/pull/466)) ### [`v1.6.2`](https://togithub.com/FormidableLabs/urql/releases/v1.6.2) [Compare Source](https://togithub.com/FormidableLabs/urql/compare/v1.6.1...v1.6.2) This fixes a potentially critical bug, where a component would enter an infinite rerender loop, when another hook triggers an update. This may happen when multiple `useQuery` hooks are used in a single component or when another state hook triggers a synchronous update. - Add generic type-parameter to `client.query` and `client.mutation`, by [@​ctrlplusb](https://togithub.com/ctrlplusb) (see [#​456](https://togithub.com/FormidableLabs/urql/pull/456)) - ⚠️ Fix `useQuery` entering an infinite loop during SSR when an update is triggered (see [#​459](https://togithub.com/FormidableLabs/urql/pull/459))

Configuration

📅 Schedule: "before 3am on the first day of the month" (UTC).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.



This PR has been generated by WhiteSource Renovate. View repository job log here.

vercel[bot] commented 4 years ago

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/iamstarkov/topics-manager/exuz03syl
✅ Preview: https://topics-manager-git-renovate-urql-1x.iamstarkov.vercel.app