dancefinder/dancefinder-app
5
0
Fork 0
Code Issues 1 Pull Requests 1 Actions Packages Projects Releases Activity

Build(deps): bump @apollo/client from 3.5.10 to 3.6.0 #338

Merged
argoyle merged 1 commits from dependabot-npm_and_yarn-apollo-client-3.6.0 into master 2022-04-28 06:25:42 +00:00
Conversation 4 Commits 1 Files Changed 2
+23 -17
argoyle commented 2022-04-27 04:38:27 +00:00 (Migrated from gitlab.com)
Copy Link
Copy Source

Bumps @apollo/client from 3.5.10 to 3.6.0.

Release notes

Sourced from @​apollo/client's releases.

3.6.0

Note: for the most up-to-date version of this information, see CHANGELOG.md

Apollo Client 3.6.0 (2022-04-26)

Potentially disruptive changes

  • Calling fetchMore for queries using the cache-and-network or network-only fetch policies will no longer trigger additional network requests when cache results are complete. Instead, those complete cache results will be delivered as if using the cache-first fetch policy. @​benjamn in #9504

  • Reimplement useQuery and useLazyQuery to use the proposed useSyncExternalStore API from React 18. @​brainkim and @​benjamn in #8785 and #9596

  • Fixed bug where the useLazyQuery execution function would always use the refetch method of ObservableQuery, instead of properly reapplying the current fetchPolicy using the reobserve method. @​benjamn in #9564

    Since this reobserve method is useful and used internally, we have now exposed it as use[Lazy]Query(...).reobserve (which optionally takes a Partial<WatchQueryOptions> of new options), to supplement the existing refetch method. Note that reobserve permanently updates the variables and other options of the ObservableQuery, unlike refetch({ ...variables }), which does not save those variables.

  • The internal use of options.fetchBlockingPromise by useQuery and useLazyQuery may slightly delay the delivery of network results, compared to previous versions of Apollo Client. Since network results are already delivered asynchronously, these timing differences should not be disruptive in most cases. Nevertheless, please open an issue if the timing differences cause problems for your applications. @​benjamn in #9599

React 18

In both its peerDependencies and its internal implementation, Apollo Client v3.6 should no longer prevent you from updating to React 18 in your applications.

Internally, we have refactored useQuery and useLazyQuery to be implemented in terms of React's new (shimmable) useSyncExternalStore hook, demonstrating Apollo Client can serve as an external store with a referentially stable, synchronous API, as needed by React.

As part of this refactoring, we also improved the behavior of useQuery and useLazyQuery when used in <React.StrictMode>, which double-renders components in development. While this double-rendering always results in calling useQuery twice, forcing Apollo Client to create and then discard an unnecessary ObservableQuery object, we now have multiple defenses in place against executing any network queries for the unused ObservableQuery objects.

In upcoming v3.6.x and v3.7 (beta) releases, we will be completely overhauling our server-side rendering utilities (getDataFromTree et al.), and introducing suspenseful versions of our hooks, to take full advantage of the new patterns React 18+ enables for data management libraries like Apollo Client.

Improvements

  • Allow BatchLink to cancel queued and in-flight operations. @​PowerKiKi and @​benjamn in #9248

  • Add GraphQLWsLink in @apollo/client/link/subscriptions. This link is similar to the existing WebSocketLink in @apollo/client/link/ws, but uses the newer graphql-ws package and protocol instead of the older subscriptions-transport-ws implementation. This functionality was technically first released in @apollo/client@3.5.10, but semantically belongs in the 3.6.0 minor version. @​glasser in #9369

  • Allow passing defaultOptions to useQuery to avoid clobbering/resetting existing options when useQuery is called repeatedly. @​benjamn in #9563, superseding #9223

  • Provide additional context to nextFetchPolicy functions to assist with fetchPolicy transitions. More details can be found in the nextFetchPolicy documentation. @​benjamn in #9222

  • Remove nagging deprecation warning about passing an options.updateQuery function to fetchMore. @​benjamn in #9504

  • Let addTypenameToDocument take any ASTNode (including DocumentNode, as before). @​benjamn in #9595

... (truncated)

Changelog

Sourced from @​apollo/client's changelog.

Apollo Client 3.6.0 (2022-04-26)

Potentially disruptive changes

  • Calling fetchMore for queries using the cache-and-network or network-only fetch policies will no longer trigger additional network requests when cache results are complete. Instead, those complete cache results will be delivered as if using the cache-first fetch policy. @​benjamn in #9504

  • Reimplement useQuery and useLazyQuery to use the proposed useSyncExternalStore API from React 18. @​brainkim and @​benjamn in #8785 and #9596

  • Fixed bug where the useLazyQuery execution function would always use the refetch method of ObservableQuery, instead of properly reapplying the current fetchPolicy using the reobserve method. @​benjamn in #9564

    Since this reobserve method is useful and used internally, we have now exposed it as use[Lazy]Query(...).reobserve (which optionally takes a Partial<WatchQueryOptions> of new options), to supplement the existing refetch method. Note that reobserve permanently updates the variables and other options of the ObservableQuery, unlike refetch({ ...variables }), which does not save those variables.

  • The internal use of options.fetchBlockingPromise by useQuery and useLazyQuery may slightly delay the delivery of network results, compared to previous versions of Apollo Client. Since network results are already delivered asynchronously, these timing differences should not be disruptive in most cases. Nevertheless, please open an issue if the timing differences are a problem for you (and you have no easy workaround). @​benjamn in #9599

React 18

In both its peerDependencies and its internal implementation, Apollo Client v3.6 should no longer prevent you from updating to React 18 in your applications.

Internally, we have refactored useQuery and useLazyQuery to be implemented in terms of React's new (shimmable) useSyncExternalStore hook, demonstrating Apollo Client can serve as an external store with a referentially stable, synchronous API, as needed by React.

As part of this refactoring, we also improved the behavior of useQuery and useLazyQuery when used in <React.StrictMode>, which double-renders components in development. While this double-rendering always results in calling useQuery twice, forcing Apollo Client to create and then discard an unnecessary ObservableQuery object, we now have multiple defenses in place against executing any network queries for the unused ObservableQuery objects.

In upcoming v3.6.x and v3.7 (beta) releases, we will be completely overhauling our server-side rendering utilities (getDataFromTree et al.), and introducing suspenseful versions of our hooks, to take full advantage of the new patterns React 18+ enables for data management libraries like Apollo Client.

Improvements

  • Allow BatchLink to cancel queued and in-flight operations. @​PowerKiKi and @​benjamn in #9248

  • Add GraphQLWsLink in @apollo/client/link/subscriptions. This link is similar to the existing WebSocketLink in @apollo/client/link/ws, but uses the newer graphql-ws package and protocol instead of the older subscriptions-transport-ws implementation. This functionality was technically first released in @apollo/client@3.5.10, but semantically belongs in the 3.6.0 minor version. @​glasser in #9369

  • Allow passing defaultOptions to useQuery to avoid clobbering/resetting existing options when useQuery is called repeatedly. @​benjamn in #9563, superseding #9223

  • Provide additional context to nextFetchPolicy functions to assist with fetchPolicy transitions. More details can be found in the nextFetchPolicy documentation. @​benjamn in #9222

  • Remove nagging deprecation warning about passing an options.updateQuery function to fetchMore. @​benjamn in #9504

  • Let addTypenameToDocument take any ASTNode (including DocumentNode, as before). @​benjamn in #9595

  • Set useMutation internal isMounted variable to true again when component remounted. @​devpeerapong in #9561

Commits
  • 04a35d5 Bump @​apollo/client npm version to 3.6.0. 🥳
  • e082176 Publish to npm with next rather than beta dist-tag.
  • 6b0fe24 Mention PR #9561 in CHANGELOG.md.
  • 95ec974 Set mutation isMounted variable to true when remounted (#9561)
  • 85e8fc3 Merge branch 'main' into release-3.6.
  • 2b295b2 chore(deps): update dependency graphql to v16.3.0 (#9182)
  • f6d183f chore(deps): update dependency rxjs to v7 (#8106)
  • 21ec87f chore(deps): update dependency @​types/node to v16.11.27 (#9604)
  • 20fb408 chore(deps): update dependency glob to v8 (#9606)
  • 516ce84 chore(deps): update dependency @​testing-library/react-hooks to v8 (#9594)
  • Additional commits viewable in compare view

Dependabot commands
You can trigger Dependabot actions by commenting on this MR
  • $dependabot rebase will rebase this MR
  • $dependabot recreate will recreate this MR rewriting all the manual changes and resolving conflicts
Bumps [@apollo/client](https://github.com/apollographql/apollo-client) from 3.5.10 to 3.6.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/apollographql/apollo-client/releases"><code>@​apollo/client</code>'s releases</a>.</em></p> <blockquote> <h2>3.6.0</h2> <blockquote> <p>Note: for the most up-to-date version of this information, see <a href="https://github.com/apollographql/apollo-client/blob/main/CHANGELOG.md"><code>CHANGELOG.md</code></a></p> </blockquote> <h2>Apollo Client 3.6.0 (2022-04-26)</h2> <h3>Potentially disruptive changes</h3> <ul> <li> <p>Calling <code>fetchMore</code> for queries using the <code>cache-and-network</code> or <code>network-only</code> fetch policies will no longer trigger additional network requests when cache results are complete. Instead, those complete cache results will be delivered as if using the <code>cache-first</code> fetch policy. <a href="https://github.com/benjamn"><code>@​benjamn</code></a> in <a href="https://github.com/apollographql/apollo-client/pull/9504">#9504</a></p> </li> <li> <p>Reimplement <code>useQuery</code> and <code>useLazyQuery</code> to use the <a href="https://github.com/reactwg/react-18/discussions/86">proposed <code>useSyncExternalStore</code> API</a> from React 18. <a href="https://github.com/brainkim"><code>@​brainkim</code></a> and <a href="https://github.com/benjamn"><code>@​benjamn</code></a> in <a href="https://github.com/apollographql/apollo-client/pull/8785">#8785</a> and <a href="https://github.com/apollographql/apollo-client/pull/9596">#9596</a></p> </li> <li> <p>Fixed bug where the <code>useLazyQuery</code> execution function would always use the <code>refetch</code> method of <code>ObservableQuery</code>, instead of properly reapplying the current <code>fetchPolicy</code> using the <code>reobserve</code> method. <a href="https://github.com/benjamn"><code>@​benjamn</code></a> in <a href="https://github.com/apollographql/apollo-client/pull/9564">#9564</a></p> <blockquote> <p>Since this <code>reobserve</code> method is useful and used internally, we have now exposed it as <code>use[Lazy]Query(...).reobserve</code> (which optionally takes a <code>Partial&lt;WatchQueryOptions&gt;</code> of new options), to supplement the existing <code>refetch</code> method. Note that <code>reobserve</code> permanently updates the <code>variables</code> and other options of the <code>ObservableQuery</code>, unlike <code>refetch({ ...variables })</code>, which does not save those <code>variables</code>.</p> </blockquote> </li> <li> <p>The internal use of <code>options.fetchBlockingPromise</code> by <code>useQuery</code> and <code>useLazyQuery</code> may slightly delay the delivery of network results, compared to previous versions of Apollo Client. Since network results are already delivered asynchronously, these timing differences should not be disruptive in most cases. Nevertheless, please <a href="https://github.com/apollographql/apollo-client/issues/new/choose">open an issue</a> if the timing differences cause problems for your applications. <a href="https://github.com/benjamn"><code>@​benjamn</code></a> in <a href="https://github.com/apollographql/apollo-client/pull/9599">#9599</a></p> </li> </ul> <h3>React 18</h3> <p>In both its <code>peerDependencies</code> and its internal implementation, Apollo Client v3.6 should no longer prevent you from updating to React 18 in your applications.</p> <p>Internally, we have refactored <code>useQuery</code> and <code>useLazyQuery</code> to be implemented in terms of React's new (shimmable) <code>useSyncExternalStore</code> hook, demonstrating Apollo Client can serve as an external store with a referentially stable, synchronous API, as needed by React.</p> <p>As part of this refactoring, we also improved the behavior of <code>useQuery</code> and <code>useLazyQuery</code> when used in <code>&lt;React.StrictMode&gt;</code>, which <a href="https://github.com/reactwg/react-18/discussions/96">double-renders components in development</a>. While this double-rendering always results in calling <code>useQuery</code> twice, forcing Apollo Client to create and then discard an unnecessary <code>ObservableQuery</code> object, we now have multiple defenses in place against executing any network queries for the unused <code>ObservableQuery</code> objects.</p> <p>In upcoming v3.6.x and v3.7 (beta) releases, we will be completely overhauling our server-side rendering utilities (<code>getDataFromTree</code> et al.), and introducing suspenseful versions of our hooks, to take full advantage of the new patterns React 18+ enables for data management libraries like Apollo Client.</p> <h3>Improvements</h3> <ul> <li> <p>Allow <code>BatchLink</code> to cancel queued and in-flight operations. <a href="https://github.com/PowerKiKi"><code>@​PowerKiKi</code></a> and <a href="https://github.com/benjamn"><code>@​benjamn</code></a> in <a href="https://github.com/apollographql/apollo-client/pull/9248">#9248</a></p> </li> <li> <p>Add <code>GraphQLWsLink</code> in <code>@apollo/client/link/subscriptions</code>. This link is similar to the existing <code>WebSocketLink</code> in <code>@apollo/client/link/ws</code>, but uses the newer <a href="https://www.npmjs.com/package/graphql-ws"><code>graphql-ws</code></a> package and protocol instead of the older <code>subscriptions-transport-ws</code> implementation. This functionality was technically first released in <code>@apollo/client@3.5.10</code>, but semantically belongs in the 3.6.0 minor version. <a href="https://github.com/glasser"><code>@​glasser</code></a> in <a href="https://github.com/apollographql/apollo-client/pull/9369">#9369</a></p> </li> <li> <p>Allow passing <code>defaultOptions</code> to <code>useQuery</code> to avoid clobbering/resetting existing options when <code>useQuery</code> is called repeatedly. <a href="https://github.com/benjamn"><code>@​benjamn</code></a> in <a href="https://github.com/apollographql/apollo-client/pull/9563">#9563</a>, superseding <a href="https://github.com/apollographql/apollo-client/pull/9223">#9223</a></p> </li> <li> <p>Provide additional context to <code>nextFetchPolicy</code> functions to assist with <code>fetchPolicy</code> transitions. More details can be found in the <a href="https://www.apollographql.com/docs/react/data/queries/#nextfetchpolicy"><code>nextFetchPolicy</code> documentation</a>. <a href="https://github.com/benjamn"><code>@​benjamn</code></a> in <a href="https://github.com/apollographql/apollo-client/pull/9222">#9222</a></p> </li> <li> <p>Remove nagging deprecation warning about passing an <code>options.updateQuery</code> function to <code>fetchMore</code>. <a href="https://github.com/benjamn"><code>@​benjamn</code></a> in <a href="https://github.com/apollographql/apollo-client/pull/9504">#9504</a></p> </li> <li> <p>Let <code>addTypenameToDocument</code> take any <code>ASTNode</code> (including <code>DocumentNode</code>, as before). <a href="https://github.com/benjamn"><code>@​benjamn</code></a> in <a href="https://github.com/apollographql/apollo-client/pull/9595">#9595</a></p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/apollographql/apollo-client/blob/main/CHANGELOG.md"><code>@​apollo/client</code>'s changelog</a>.</em></p> <blockquote> <h2>Apollo Client 3.6.0 (2022-04-26)</h2> <h3>Potentially disruptive changes</h3> <ul> <li> <p>Calling <code>fetchMore</code> for queries using the <code>cache-and-network</code> or <code>network-only</code> fetch policies will no longer trigger additional network requests when cache results are complete. Instead, those complete cache results will be delivered as if using the <code>cache-first</code> fetch policy. <!-- raw HTML omitted --> <a href="https://github.com/benjamn"><code>@​benjamn</code></a> in <a href="https://github.com/apollographql/apollo-client/pull/9504">#9504</a></p> </li> <li> <p>Reimplement <code>useQuery</code> and <code>useLazyQuery</code> to use the <a href="https://github.com/reactwg/react-18/discussions/86">proposed <code>useSyncExternalStore</code> API</a> from React 18. <!-- raw HTML omitted --> <a href="https://github.com/brainkim"><code>@​brainkim</code></a> and <a href="https://github.com/benjamn"><code>@​benjamn</code></a> in <a href="https://github.com/apollographql/apollo-client/pull/8785">#8785</a> and <a href="https://github.com/apollographql/apollo-client/pull/9596">#9596</a></p> </li> <li> <p>Fixed bug where the <code>useLazyQuery</code> execution function would always use the <code>refetch</code> method of <code>ObservableQuery</code>, instead of properly reapplying the current <code>fetchPolicy</code> using the <code>reobserve</code> method. <!-- raw HTML omitted --> <a href="https://github.com/benjamn"><code>@​benjamn</code></a> in <a href="https://github.com/apollographql/apollo-client/pull/9564">#9564</a></p> <blockquote> <p>Since this <code>reobserve</code> method is useful and used internally, we have now exposed it as <code>use[Lazy]Query(...).reobserve</code> (which optionally takes a <code>Partial&lt;WatchQueryOptions&gt;</code> of new options), to supplement the existing <code>refetch</code> method. Note that <code>reobserve</code> permanently updates the <code>variables</code> and other options of the <code>ObservableQuery</code>, unlike <code>refetch({ ...variables })</code>, which does not save those <code>variables</code>.</p> </blockquote> </li> <li> <p>The internal use of <code>options.fetchBlockingPromise</code> by <code>useQuery</code> and <code>useLazyQuery</code> may slightly delay the delivery of network results, compared to previous versions of Apollo Client. Since network results are already delivered asynchronously, these timing differences should not be disruptive in most cases. Nevertheless, please open an issue if the timing differences are a problem for you (and you have no easy workaround). <!-- raw HTML omitted --> <a href="https://github.com/benjamn"><code>@​benjamn</code></a> in <a href="https://github.com/apollographql/apollo-client/pull/9599">#9599</a></p> </li> </ul> <h3>React 18</h3> <p>In both its <code>peerDependencies</code> and its internal implementation, Apollo Client v3.6 should no longer prevent you from updating to React 18 in your applications.</p> <p>Internally, we have refactored <code>useQuery</code> and <code>useLazyQuery</code> to be implemented in terms of React's new (shimmable) <code>useSyncExternalStore</code> hook, demonstrating Apollo Client can serve as an external store with a referentially stable, synchronous API, as needed by React.</p> <p>As part of this refactoring, we also improved the behavior of <code>useQuery</code> and <code>useLazyQuery</code> when used in <code>&lt;React.StrictMode&gt;</code>, which <a href="https://github.com/reactwg/react-18/discussions/96">double-renders components in development</a>. While this double-rendering always results in calling <code>useQuery</code> twice, forcing Apollo Client to create and then discard an unnecessary <code>ObservableQuery</code> object, we now have multiple defenses in place against executing any network queries for the unused <code>ObservableQuery</code> objects.</p> <p>In upcoming v3.6.x and v3.7 (beta) releases, we will be completely overhauling our server-side rendering utilities (<code>getDataFromTree</code> et al.), and introducing suspenseful versions of our hooks, to take full advantage of the new patterns React 18+ enables for data management libraries like Apollo Client.</p> <h3>Improvements</h3> <ul> <li> <p>Allow <code>BatchLink</code> to cancel queued and in-flight operations. <!-- raw HTML omitted --> <a href="https://github.com/PowerKiKi"><code>@​PowerKiKi</code></a> and <a href="https://github.com/benjamn"><code>@​benjamn</code></a> in <a href="https://github.com/apollographql/apollo-client/pull/9248">#9248</a></p> </li> <li> <p>Add <code>GraphQLWsLink</code> in <code>@apollo/client/link/subscriptions</code>. This link is similar to the existing <code>WebSocketLink</code> in <code>@apollo/client/link/ws</code>, but uses the newer <a href="https://www.npmjs.com/package/graphql-ws"><code>graphql-ws</code></a> package and protocol instead of the older <code>subscriptions-transport-ws</code> implementation. This functionality was technically first released in <code>@apollo/client@3.5.10</code>, but semantically belongs in the 3.6.0 minor version. <a href="https://github.com/glasser"><code>@​glasser</code></a> in <a href="https://github.com/apollographql/apollo-client/pull/9369">#9369</a></p> </li> <li> <p>Allow passing <code>defaultOptions</code> to <code>useQuery</code> to avoid clobbering/resetting existing options when <code>useQuery</code> is called repeatedly. <!-- raw HTML omitted --> <a href="https://github.com/benjamn"><code>@​benjamn</code></a> in <a href="https://github.com/apollographql/apollo-client/pull/9563">#9563</a>, superseding <a href="https://github.com/apollographql/apollo-client/pull/9223">#9223</a></p> </li> <li> <p>Provide additional context to <code>nextFetchPolicy</code> functions to assist with <code>fetchPolicy</code> transitions. More details can be found in the <a href="https://www.apollographql.com/docs/react/data/queries/#nextfetchpolicy"><code>nextFetchPolicy</code> documentation</a>. <!-- raw HTML omitted --> <a href="https://github.com/benjamn"><code>@​benjamn</code></a> in <a href="https://github.com/apollographql/apollo-client/pull/9222">#9222</a></p> </li> <li> <p>Remove nagging deprecation warning about passing an <code>options.updateQuery</code> function to <code>fetchMore</code>. <!-- raw HTML omitted --> <a href="https://github.com/benjamn"><code>@​benjamn</code></a> in <a href="https://github.com/apollographql/apollo-client/pull/9504">#9504</a></p> </li> <li> <p>Let <code>addTypenameToDocument</code> take any <code>ASTNode</code> (including <code>DocumentNode</code>, as before). <!-- raw HTML omitted --> <a href="https://github.com/benjamn"><code>@​benjamn</code></a> in <a href="https://github.com/apollographql/apollo-client/pull/9595">#9595</a></p> </li> <li> <p>Set <code>useMutation</code> internal <code>isMounted</code> variable to <code>true</code> again when component remounted. <!-- raw HTML omitted --> <a href="https://github.com/devpeerapong"><code>@​devpeerapong</code></a> in <a href="https://github.com/apollographql/apollo-client/pull/9561">#9561</a></p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/apollographql/apollo-client/commit/04a35d50cd213762a4004eb33fee3cd8fdf38261"><code>04a35d5</code></a> Bump <code>@​apollo/client</code> npm version to 3.6.0. :partying_face:</li> <li><a href="https://github.com/apollographql/apollo-client/commit/e082176c47b45969c47cb9339fb43232769c4cfb"><code>e082176</code></a> Publish to npm with next rather than beta dist-tag.</li> <li><a href="https://github.com/apollographql/apollo-client/commit/6b0fe243092a32bf8beec9318ec5e74f0f31f394"><code>6b0fe24</code></a> Mention PR <a href="https://github.com/apollographql/apollo-client/issues/9561">#9561</a> in CHANGELOG.md.</li> <li><a href="https://github.com/apollographql/apollo-client/commit/95ec97446e2e997eda7fb6969323a474326c77af"><code>95ec974</code></a> Set mutation isMounted variable to true when remounted (<a href="https://github.com/apollographql/apollo-client/issues/9561">#9561</a>)</li> <li><a href="https://github.com/apollographql/apollo-client/commit/85e8fc3bd198ab04e0c16c3a27054425cbc3f905"><code>85e8fc3</code></a> Merge branch 'main' into release-3.6.</li> <li><a href="https://github.com/apollographql/apollo-client/commit/2b295b29c026bae0e105f5a81a49fa3d032b864c"><code>2b295b2</code></a> chore(deps): update dependency graphql to v16.3.0 (<a href="https://github.com/apollographql/apollo-client/issues/9182">#9182</a>)</li> <li><a href="https://github.com/apollographql/apollo-client/commit/f6d183f90c6fae8ef2cbfd1cfc6333ec8737f34e"><code>f6d183f</code></a> chore(deps): update dependency rxjs to v7 (<a href="https://github.com/apollographql/apollo-client/issues/8106">#8106</a>)</li> <li><a href="https://github.com/apollographql/apollo-client/commit/21ec87fd3013897db47e561edb8d54a7cc410737"><code>21ec87f</code></a> chore(deps): update dependency <code>@​types/node</code> to v16.11.27 (<a href="https://github.com/apollographql/apollo-client/issues/9604">#9604</a>)</li> <li><a href="https://github.com/apollographql/apollo-client/commit/20fb4088166b2cb74a7efaf9455d6dc59021d953"><code>20fb408</code></a> chore(deps): update dependency glob to v8 (<a href="https://github.com/apollographql/apollo-client/issues/9606">#9606</a>)</li> <li><a href="https://github.com/apollographql/apollo-client/commit/516ce84c368d75ae73f65bf5a9c8cba250e049d8"><code>516ce84</code></a> chore(deps): update dependency <code>@​testing-library/react-hooks</code> to v8 (<a href="https://github.com/apollographql/apollo-client/issues/9594">#9594</a>)</li> <li>Additional commits viewable in <a href="https://github.com/apollographql/apollo-client/compare/v3.5.10...v3.6.0">compare view</a></li> </ul> </details> <br /> --- <details> <summary>Dependabot commands</summary> <br /> You can trigger Dependabot actions by commenting on this MR - `$dependabot rebase` will rebase this MR - `$dependabot recreate` will recreate this MR rewriting all the manual changes and resolving conflicts </details>
argoyle commented 2022-04-27 06:15:24 +00:00 (Migrated from gitlab.com)
Copy Link
Copy Source

added 3 commits

  • fbf76810...24ea28b2 - 2 commits from branch master
  • 9a260774 - Build(deps): bump @apollo/client from 3.5.10 to 3.6.0

Compare with previous version

added 3 commits <ul><li>fbf76810...24ea28b2 - 2 commits from branch <code>master</code></li><li>9a260774 - Build(deps): bump @apollo/client from 3.5.10 to 3.6.0</li></ul> [Compare with previous version](/unboundsoftware/dancefinder/dancefinder-app/-/merge_requests/289/diffs?diff_id=381839382&start_sha=fbf76810496dbe2902486b86bcede9e3fe75db92)
argoyle commented 2022-04-28 05:35:50 +00:00 (Migrated from gitlab.com)
Copy Link
Copy Source

added 3 commits

  • 9a260774...e8091896 - 2 commits from branch master
  • 5771edf5 - Build(deps): bump @apollo/client from 3.5.10 to 3.6.0

Compare with previous version

added 3 commits <ul><li>9a260774...e8091896 - 2 commits from branch <code>master</code></li><li>5771edf5 - Build(deps): bump @apollo/client from 3.5.10 to 3.6.0</li></ul> [Compare with previous version](/unboundsoftware/dancefinder/dancefinder-app/-/merge_requests/289/diffs?diff_id=382812023&start_sha=9a2607747fdd9f953a0ea7da02fabdfc8a8db01b)
argoyle commented 2022-04-28 05:47:16 +00:00 (Migrated from gitlab.com)
Copy Link
Copy Source

added 3 commits

  • 5771edf5...bddee56a - 2 commits from branch master
  • 93b4048b - Build(deps): bump @apollo/client from 3.5.10 to 3.6.0

Compare with previous version

added 3 commits <ul><li>5771edf5...bddee56a - 2 commits from branch <code>master</code></li><li>93b4048b - Build(deps): bump @apollo/client from 3.5.10 to 3.6.0</li></ul> [Compare with previous version](/unboundsoftware/dancefinder/dancefinder-app/-/merge_requests/289/diffs?diff_id=382816422&start_sha=5771edf5c6624b444fd2e92ba9f16e9c451bde98)
argoyle (Migrated from gitlab.com) scheduled this pull request to auto merge when all checks succeed 2022-04-28 06:14:18 +00:00
argoyle commented 2022-04-28 06:25:42 +00:00 (Migrated from gitlab.com)
Copy Link
Copy Source

mentioned in commit 78da5d7476

mentioned in commit 78da5d74769139a9a6248e1d73d37b66a87524a3
argoyle (Migrated from gitlab.com) merged commit 78da5d7476 into master 2022-04-28 06:25:42 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
dependencies
Pull requests that update a dependency file
 docker
javascript
security
Pull requests that address a security vulnerability
 severity:critical
severity:high
severity:low
severity:moderate
No Label dependencies javascript
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
argoyle (Joakim Olsson) buildtools (Buildtools) kubernetes (Kubernetes) releaser (Unbound Releaser) renovate (Renovate Bot)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dancefinder/dancefinder-app#338
Delete Branch "dependabot-npm_and_yarn-apollo-client-3.6.0"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?