chore(deps): update apollo graphql packages

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
apollo-cache-inmemory	1.2.2 -> 1.6.6
apollo-client	2.3.1 -> 2.6.10
apollo-codegen	^0.19.1 -> ^0.20.0
graphql-tag	2.9.2 -> 2.12.6
react-apollo	2.1.4 -> 2.5.8

---

Release Notes

apollographql/apollo-client (apollo-cache-inmemory)

v1.6.6

Compare Source

v1.6.5

Compare Source

v1.6.3

Compare Source

v1.6.2

Compare Source

v1.6.1

Compare Source

• Pretend that __typename exists on the root Query when matching fragments.
  
  @​benjamn in #​4853

v1.6.0

Compare Source

• Support new InMemoryCache({ freezeResults: true }) to help enforce immutability.
  
  @​benjamn in #​4514

• Allow IntrospectionFragmentMatcher to match fragments against the root Query, as HeuristicFragmentMatcher does.
  
  @​rynobax in #​4620

• Rerential identity (===) of arrays in cache results will now be preserved for unchanged data.
  
  @​benjamn in commit f3091d6a

• Avoid adding __typename field to @client selection sets that have been @exported as input variables.
  
  @​benjamn in #​4784

v1.5.1

Compare Source

v1.5.0

Compare Source

v1.4.3

Compare Source

v1.4.2

Compare Source

v1.4.1

Compare Source

• The optimism npm package has been updated to a version (0.6.9) that
  provides its own TypeScript declarations, which should fix problems like
  Issue #​4327.
  
  PR #​4331

• Error messages involving GraphQL queries now print the queries using
  JSON.stringify instead of the print function exported by the
  graphql package, to avoid pulling unnecessary printing logic into your
  JavaScript bundle.
  
  PR #​4234

• The QueryKeyMaker abstraction has been removed, meaning that cache
  results for non-identical queries (or sub-queries) with equivalent
  structure will no longer be cached together. This feature was a nice
  optimization in certain specific use cases, but it was not worth the
  additional complexity or bundle size.
  
  PR #​4245

v1.4.0

Compare Source

• The speed and memory usage of optimistic reads and writes has been
  improved dramatically using a new layering technique that does not
  require copying the non-optimistic contents of the cache.
  
  PR #​4319

• The RecordingCache abstraction has been removed, and thus is no longer
  exported from apollo-cache-inmemory.
  
  PR #​4319

• Export the optimism wrap function using ES2015 export syntax, instead of
  CommonJS.
  
  @​ardatan in #​4158

v1.3.12

Compare Source

• Avoid using DepTrackingCache for optimistic reads.
  PR #​4521

• When creating an InMemoryCache object, it's now possible to disable the
  result caching behavior introduced in #​3394,
  either for diagnostic purposes or because the benefit of caching repeated
  reads is not worth the extra memory usage in your application:

  new InMemoryCache({
    resultCaching: false,
  });

  Part of PR #​4521.

v1.3.11

Compare Source

• No changes.

v1.3.10

Compare Source

• Added some returns to prevent errors with noImplicitReturns
  TypeScript rule.
  PR #​4137

• Exclude the src/ directory when publishing apollo-cache-inmemory.
  Issue #​4083

v1.3.9

Compare Source

• Avoid modifying source objects when merging cache results.
  Issue #​4081
  PR #​4089

v1.3.8

Compare Source

v1.3.7

Compare Source

• Throw when querying non-scalar objects without a selection set.
  Issue #​4025
  PR #​4038

• Work around spec non-compliance of Map#set and Set#add in IE11.
  Issue #​4024
  PR #​4012

v1.3.6

Compare Source

• Optimize repeated apollo-cache-inmemory reads by caching partial query
  results, for substantial performance improvements. As a consequence, watched
  queries will not be rebroadcast unless the data have changed.
  PR #​3394

• Include root ID and fragment matcher function in cache keys computed by
  StoreReader#executeStoreQuery and executeSelectionSet, and work
  around bugs in the React Native Map and Set polyfills.
  PR #​3964
  React Native PR #​21492 (pending)

• The apollo-cache-inmemory package now allows graphql@^14.0.0 as a
  peer dependency.
  Issue #​3978

• The apollo-cache-inmemory package now correctly broadcasts changes
  even when the new data is === to the old data, since the contents of
  the data object may have changed.
  Issue #​3992
  PR #​4032

v1.3.5

Compare Source

v1.3.4

Compare Source

v1.3.3

Compare Source

v1.3.2

• Reimplement isEqual without pulling in massive lodash.isequal.
  
  @​benjamn in #​4924

v1.3.1

• The isEqual function has been reimplemented using the lodash.isequal npm package, to better support circular references. Since the lodash.isequal package is already used by react-apollo, this change is likely to decrease total bundle size.
  
  @​capaj in #​4915

v1.3.0

Compare Source

v1.2.10

Compare Source

• No changes.

v1.2.9

Compare Source

• Various internal infrastructure changes related to building, bundling,
  testing, etc.
  @​hwillson in #​3817

v1.2.8

Compare Source

• Fix typo in console.warn regarding fragment matching error message.
  
  @​combizs in #​3701

v1.2.7

Compare Source

• No changes.

v1.2.6

Compare Source

• Add __typename and id properties to dataIdFromObject parameter
  (typescript)
  
  @​jfurler in #​3641
• Fixed an issue caused by dataIdFromObject considering returned 0 values to
  be falsy, instead of being a valid ID, which lead to the store not being
  updated properly in some cases.
  
  @​hwillson in #​3711

v1.2.5

Compare Source

• No changes.

v1.2.4

Compare Source

• No changes

v1.2.3

Compare Source

• Added optional generics to cache manipulation methods (typescript).
  (@​mvestergaard in #​3541)
• Restore non-enumerability of resultFields[ID_KEY].
  (@​benjamn in #​3544)
• Cache query documents transformed by InMemoryCache.
  (@​benjamn in #​3553)

apollographql/apollo-codegen (apollo-codegen)

v0.20.2

Compare Source

• The TypeScript and Flow targets now use block comments to better handle multiline comments in schemas
• Fix crash when running on a version of Node that already supports Array.flatMap

v0.20.1

Compare Source

• Fix issue with flow-legacy target being unusable

v0.20.0

Compare Source

• BREAKING: The typescript and flow targets now refer to the modern implementations. The deprecated legacy targets are available under typescript-legacy and flow-legacy.
• BREAKING: The --output parameter to the CLI is now required for all targets.
• The TypeScript and Flow targets now support outputting types to either a single file or a directory, where types for each query will be separated

apollographql/graphql-tag (graphql-tag)

v2.12.6

Compare Source

• Update peer dependencies to allow graphql ^16.0.0.
  
  @​brainkim in #​530

v2.12.5

Compare Source

• Also publish src/ directory to npm, enabling source maps.
  
  @​maclockard in #​403

v2.12.4

Compare Source

• Allow fragments to be imported by name when using the webpack loader.
  
  @​dobesv in #​257

v2.12.3

Compare Source

• Update tslib dependency to version 2.1.0.
  
  @​benjamn in #​381

v2.12.2

Compare Source

• Avoid using Object.assign to attach extra properties to gql.
  
  @​benjamn in #​380

v2.12.1

Compare Source

• To accommodate older versions of TypeScript, usage of the import type ... syntax (introduced by #​325) has been removed, fixing issue #​345.
  
  @​benjamn in #​352

v2.12.0

Compare Source

• The graphql-tag repository has been converted to TypeScript, adding type safety and enabling both ECMAScript and CommonJS module exports. While these changes are intended to be as backwards-compatible as possible, we decided to bump the minor version to reflect the significant refactoring.
  
  @​PowerKiKi and @​benjamn in #​325

v2.11.0

Compare Source

• package.json sideEffects changes to clearly identify that graphql-tag doesn't have side effects.
  
  @​hwillson in #​313

v2.10.4

Compare Source

• Bump dev/peer deps to accommodate graphql 15.
  
  @​adriencohen in #​299

v2.10.3

Compare Source

• Further adjustments to the TS index.d.ts declaration file.
  
  @​Guillaumez in #​289

v2.10.2

Compare Source

• Update/fix the existing TS index.d.ts declaration file.
  
  @​hwillson in #​285

v2.10.1

Compare Source

• Fix failures in IE11 by avoiding unsupported (by IE11) constructor arguments to Set by rocwang in #​190

v2.10.0

Compare Source

• Add support for graphql@14 by timsuchanek in #​210, #​211

apollographql/react-apollo (react-apollo)

v2.5.8

Compare Source

2.5.8 (2019-06-21)

Bug Fixes

• Makes the use of apollo-client 2.6.3's ObservableQuery.resetQueryStoreErrors
  method optional, for people who can't update to react-apollo's new
  apollo-client peer dep of 2.6.3.
  @​hwillson in #​3151

v2.5.7

Compare Source

Improvements

• Make sure MockedProvider is using the proper CJS/ESM bundle, when
  referencing ApolloProvider.
  
  @​jure in #​3029.
• Adjust the ApolloContext definition to play a bit more nicely with
  React.createContext types.
  
  @​JoviDeCroock in #​3018
• The result of a mutation is now made available to the wrapped component,
  when using the graphql HOC.
  
  @​andycarrell in #​3008
• Check equality of stringified variables in the MockLink to improve
  debugging experience used by MockedProvider.
  
  @​evans in #​3078

Bug Fixes

• Removed leftover apollo-client@beta peer dep.
  
  @​brentertz in #​3064
• Stop setting optional input to null, when using the graphql HOC.
  
  @​ZhengYuTay in #​3056
• Fix typescript error caused by query being mandatory in the fetchMore signature.
  
  @​HsuTing in #​3065
• Fixes an issue that caused the Query component to get stuck in an always
  loading state, caused by receiving an error (meaning subsequent valid
  responses couldn't be handled). The Query component can now handle an
  error in a response, then continue to handle a valid response afterwards.
  
  @​hwillson in #​3107
• Reorder Subscription component code to avoid setting state on unmounted
  component.
  
  @​jasonpaulos in #​3139
• Fix component stuck in loading state for network-only fetch policy.
  
  @​jasonpaulos in #​3126

v2.5.6

Compare Source

Improvements

• Both the Query component and graphql HOC now accept a
  returnPartialData prop. This is an important new feature, that should
  help address a lot of open Apollo Client / React Apollo issues, so we'll
  explain it here with an example. Before this release, if you run a query
  that looks like:

  const GET_MEMBER = gql`
    query GetMember($id: ID!) {
      member(id: $id) {
        id
        name
      }
    }
  `;

  in one component, the results are cached, then you run a superset query like
  the following in another component:

  const GET_MEMBER_WITH_PLANS = gql`
    query GetMemberWithPlans($id: ID!) {
      member(id: $id) {
        id
        name
        plans {
          id
          title
          duration
        }
      }
    }
  `;

  Apollo Client will not re-use the partial data that was cached from the first
  query, when it preps and displays the second component. It can't find a
  cache hit for the full second query, so it fires the full query over the
  network.

  With this release, if you set a returnPartialData prop to true on the
  second component, the data available to that component will be
  automatically pre-loaded with the parts of the query that can be found in the
  cache, before the full query is fired over the network. This means you can
  do things like showing partial data in your components, while the rest of the
  data is being loaded over the network.

v2.5.5

Compare Source

Improvements

• Export the Apollo Context provider (ApolloContext).
  
  @​MrLoh in #​2961

v2.5.4

Compare Source

Bug Fixes

• Fixes Could not find "client" in the context of ApolloConsumer errors when
  using MockedProvider.
  
  @​hwillson in #​2907
• Ensure Query components using a fetchPolicy of no-cache have their
  data preserved when the components tree is re-rendered.
  
  @​hwillson in #​2914

Improvements

• Documentation updates.
  
  @​afenton90 in #​2932

v2.5.3

Compare Source

Bug Fixes

• Fixed an infinite loop caused by using setState in the
  onError / onCompleted callbacks of the Query component.
  
  @​chenesan in #​2751
• Fixed an issue that prevented good results from showing up in a Query
  component, after an error was received, variables were adjusted, and then
  the good data was fetched.
  
  @​MerzDaniel in #​2718
• Fixed an issue that prevented Query component updates from firing (under
  certain circumstances) due to the internal lastResult value (that's used
  to help prevent unnecessary re-renders) not being updated.
  
  @​Glennrs in #​2840

Improvements

• MockedProvider now accepts a childProps prop that can be used to pass
  props down to a child component.
  
  @​miachenmtl in #​2482

• onCompleted callbacks now use a destructuring-friendly type definition.
  
  @​jozanza in #​2496

• @connection directives are now properly stripped from MockedResponse's,
  when using MockedProvider.
  
  @​ajmath in #​2523

• MockedProvider has been updated to stop setting a default resolvers
  value of {}, which means by default Apollo Client 2.5 local resolver
  functionality is not enabled when mocking with MockedProvider. This allows
  @client fields to be passed through the mocked link chain, like people
  were used to before AC 2.5. When using this default mode you will see a
  dev only warning message about this like:

  Found @​client directives in query but no client resolvers were specified.
  You can now pass apollo-link-state resolvers to the ApolloClient
  constructor.

  This message can be safely ignored. If you want to use MockedProvider
  with AC 2.5's new local resolver functionality, you can pass your local
  resolver map into the MockedProvider resolvers prop.
  
  @​ajmath in #​2524

• Improvements to the graphql HOC generics for fetchMore and refetch.
  
  @​EricMcRay in #​2525

• The ApolloProvider / ApolloConsumer implementations have been refactored
  to use React 16.3's new context API.
  
  @​wzrdzl in #​2540

• All dependencies and devDependencies have been updated to their latest
  versions, and related Typescript changes have been applied.
  
  @​hwillson in #​2873

v2.5.2

Compare Source

Bug Fixes

• Export Context type from types.ts instead of walkTree.ts,
  to reenable import { Context } from 'react-apollo' (which has been
  broken since 2.4.0).
  
  @​benjamn in #​2825

Improvements

• Add examples/rollup
  to enable application-level bundle measurement and demonstrate Rollup configuration best practices.
  
  @​benjamn in #​2839

• Bundle size reductions inspired by examples/rollup app.
  
  @​benjamn in #​2842

v2.5.1

Compare Source

Bug Fixes

• Make sure MockedProvider enables Apollo Client 2.5's local state handling,
  and allow custom / mocked resolvers to be passed in as props, and used with
  the created test ApolloClient instance.
  
  @​hwillson in #​2825

v2.5.0

Compare Source

Improvements

• Ready to be used with Apollo Client 2.5 and its new local state management
  features, as well as many overall code improvements to help reduce the React
  Apollo bundle size.
  
  #​2758
• A function can now be set as a MockedResponse result when using
  MockedProvider, such that every time the mocked result is returned,
  the function is run to calculate the result. This opens up new testing
  possibilities, like being able to verify if a mocked result was actually
  requested and received by a test.
  
  @​hwillson in #​2788

v2.4.1

Compare Source

Improvements

• Adds a onSubscriptionComplete prop to the Subscription component, that
  can be passed a callback to be called when the subscription observable
  is completed.
  
  @​sujeetsr in #​2716

• During server-side rendering, ObservableQuery objects created in
  previous rendering passes will now be preserved in later passes (within
  the same getDataFromTree or getMarkupFromTree call), so that errors
  can be handled properly when using the errorPolicy: "all" option.
  
  PR #​2753

v2.4.0

Compare Source

Bug Fixes

• Invoke onCompleted/onError even if Mutation unmounts.
  
  PR #​2710

Improvements

• The walkTree function has been deprecated, since there's no way to
  make its behavior consistent with the latest versions of React. To save
  bundle size, walkTree is no longer exported from react-apollo,
  though you can still access it as follows:

  import { walkTree } from 'react-apollo/walkTree';

v2.3.3

Compare Source

Bug Fixes

• Add react-dom as a peer dependency (since it's used by getDataFromTree
  and renderToStringWithData).
  
  @​hwillson in #​2660

Improvements

• Drop react 14.x support, since the 14.x release line is 2 years old now,
  and react-apollo is no longer tested against it.
  
  @​hwillson in #​2660

v2.3.2

Compare Source

Improvements

Bug Fixes

• This package no longer imports react-dom/server unconditionally at the
  top level, making react-apollo safer to use in environments like React
  Native that are neither browser-like nor Node-like, and thus struggle to
  import react-dom/server and its dependencies. Additionally, the React
  Native bundler has been instructed to ignore all react-dom/server
  dependencies within react-apollo, so react-dom will not be bundled
  in React Native apps simply because they import react-apollo.
  PR #​2627

v2.3.1

Compare Source

Improvements

• Restore original getDataFromTree(tree, context) API, and introduce a
  new alternative called getMarkupFromTree to enable custom rendering
  functions:

  export default function getDataFromTree(
    tree: React.ReactNode,
    context: { [key: string]: any } = {},
  ) {
    return getMarkupFromTree({
      tree,
      context,
      renderFunction: renderToStaticMarkup,
    });
  }
  
  export type GetMarkupFromTreeOptions = {
    tree: React.ReactNode;
    context?: { [key: string]: any };
    renderFunction?: typeof renderToStaticMarkup;
  };
  
  export function getMarkupFromTree({
    tree,
    context = {},
    renderFunction = renderToStaticMarkup,
  }: GetMarkupFromTreeOptions): Promise<string> {...}

  PR #​2586

Bug Fixes

• Version 2.3.0 was published incorrectly, breaking nested
  react-apollo/... imports. This problem was fixed in version 2.3.1 by
  running npm publish from the lib/ directory, as intended.
  Issue #​2591

v2.3.0

Compare Source

Bug Fixes

• Fix networkStatus to reflect the loading state correctly for partial
  refetching.
  
  @​steelbrain in #​2493

Improvements

• Reimplement getDataFromTree using ReactDOM.renderToStaticMarkup to
  make asynchronous server-side rendering compatible with
  React hooks.
  Although the rendering function used by getDataFromTree defaults to
  renderToStaticMarkup, any suitable rendering function can be passed as
  the optional second argument to getDataFromTree, which now returns a
  Promise<string> that resolves to The HTML rendered in the final pass,
  which means calling renderToString after getDataFromTree may not be
  necessary anymore.
  PR #​2533

v2.2.4

Compare Source

Bug Fixes

• lodash.isequal was improperly set as a dev dependency for
  MockLink / MockedProvider. It is now a dependency.
  
  @​danilobuerger in #​2449

Improvements

• The Subscription component now accepts a fetchPolicy prop.
  
  @​MatthieuLemoine in #​2298

Typescript

• Make sure the TVariables generic is passed to ObservableQuery.
  
  @​tgriesser in #​2311

v2.2.3

Compare Source

Bug Fixes

• Mutation errors are now properly returned as a render prop, when using
  a default errorPolicy of all.
  
  @​amacleay in #​2374
• <Mutation /> refetchQueries triggered by name (string) will now use the correct variables.
  
  @​fracmal in #​2422

Improvements

• Replace the lodash dependency with lodash.flowright (since that's the
  only non-dev lodash function we're dependent on). Dev lodash
  dependencies have also been updated to use their individual module
  equivalent.
  
  @​hwillson in #​2435
• Removed rollup-plugin-babel-minify as it's no longer being used.
  
  @​hwillson in #​2436
• Small getDataFromTree.ts logic adjustment to avoid unnecessary calls
  when a falsy element is encountered.
  
  @​HOUCe in #​2429
• graphql 14 updates.
  
  @​hwillson in #​2437
• All example apps (included in the repo) have been updated to work with the
  latest version of React Apollo.
  
  @​hwillson in #​2439

Typescript

• Fix lodash typings.
  
  @​williamboman in #​2430
• Typings: added context to MutationOptions.
  
  @​danilobuerger in #​2354
• Typings: more MutationOptions changes/fixes.
  
  @​danilobuerger in #​2340
• Remove allowSyntheticDefaultImports use. Typescript's
  allowSyntheticDefaultImports compiler option is something we'd like to
  start using, but we jumped the gun a bit by introducing it in
  apollographql/react-apollo@9a96519.
  Including it means that anyone who wants to use Typescript with React
  Apollo would have to also include it in their own local tsconfig.json, to
  be able to handle default imports properly. This is because we're also using
  Typescript's es2015 module option, which means
  allowSyntheticDefaultImports has to be enabled explicitly. We've
  switched back to using a combination of import * as X and require
  syntax, to work with default imports. We'll re-introduce
  allowSyntheticDefaultImports use in React Apollo 3.
  
  @​hwillson in #​2438

v2.2.2

Compare Source

• When using React.createContext and SSR, we now make sure the context
  provider value is reset to the previous value it had after its children are
  walked.
  
  @​mitchellhamilton in #​2304
• Revert:
  
  When a query failed on the first result, the query result data was being
  returned as undefined. This behavior has been changed so that data is
  returned as an empty object. This makes checking for data (e.g.
  instead of data && data.user you can just check data.user) and
  destructring (e.g. { data: { user } }) easier. Note: this could
  potentially hurt applications that are relying on a falsey check of data
  to see if any query errors have occurred. A better (and supported) way to
  check for errors is to use the result errors property.
  
  #​1983

v2.2.1

Compare Source

• Revert: "Typescript: use Partial<TData> instead of TData | {}, for the
  QueryResult data property."

v2.2.0

• Improved TypeScript Typings:
  Deprecated MutationFunc in favor of MutationFn.
  Added missing onCompleted and onError callbacks to MutationOpts.
  
  @​danilobuerger in #​2322
• Added an example app that shows how to test mutations.
  
  @​excitement-engineer in #​1998
• The <Subscription /> component now allows the registration of a callback
  function, that will be triggered each time the component receives data. The
  callback options object param consists of the current Apollo Client
  instance in client, and the received subscription data in
  subscriptionData.
  
  @​jedwards1211 in #​1966
• The graphql options object is no longer mutated, when calculating
  variables from props. This now prevents an issue where components created
  with graphql were not having their query variables updated properly, when
  props changed.
  
  @​ksmth in #​1968
• When a query failed on the first result, the query result data was being
  returned as undefined. This behavior has been changed so that data is
  returned as an empty object. This makes checking for data (e.g.
  instead of data && data.user you can just check data.user) and
  destructring (e.g. { data: { user } }) easier. Note: this could
  potentially hurt applications that are relying on a falsey check of data
  to see if any query errors have occurred. A better (and supported) way to
  check for errors is to use the result errors property.
  
  @​TLadd in #​1983
• Allow a custom cache object to be passed into the test-utils
  MockedProvider.
  
  @​palmfjord in #​2254
• Make the MockedProvider mocks prop read only.
  
  @​amacleay in #​2284
• Remove duplicate FetchMoreOptions and FetchMoreQueryOptions types, and
  instead import them from Apollo Client.
  
  @​skovy in #​2281
• Type changes for the graphql HOC options.skip property.
  
  @​jameslaneconkling in #​2208
• Avoid importing lodash directly.
  
  @​shahyar in #​2045
• When the Query skip prop is set to true, make sure the render prop
  loading param is set to false, since we're not actually loading
  anything.
  
  @​edorivai in #​1916
• No longer building against Node 9
  
  @​hwillson in #​2404
• Make sure <Subscription />, <Query /> & <Mutation /> all support
  using an Apollo Client instance configured in the context or via
  props.
  
  @​quentin- in #​1956
• Typescript: use Partial<TData> instead of TData | {}, for the
  QueryResult data property.
  
  @​tgriesser in #​2313
• Adjust <Query /> onCompleted and onError callbacks to be triggered
  via the componentDidUpdate lifecycle method. This ensures these callbacks
  can be used when data is fetched over the network, and when data is
  fetched from the local store (previsouly these callbacks were only being
  triggered when data was fetched over the network).
  @​olistic in #​2190
• Import lodash/flowRight using ES import to allow for treeshaking.
  
  @​Pajn in #​2332
• Fixed a regression where variables passed in graphql HOC options were
  not merged with mutation variables.
  
  @​samginn in #​2216
• Added a new partialRefetch prop (false by default).
  When a Query component is mounted, and a mutation is executed
  that returns the same ID as the mounted Query, but has less
  fields in its result, Apollo Client's QueryManager returns the
  data as an empty Object since a hit can't be found in the cache.
  This can lead to application errors when the UI elements rendered by
  the original Query component are expecting certain data values to
  exist, and they're all of a sudden stripped away. The recommended way to
  handle this is to use the mutations update prop to reconcile the mutation
  result with the data in the cache, getting everything into the expected
  state. This can definitely be a cumbersome process however, so to help
  address this the partialRefetch prop can be used to automatically
  refetch the original query and update the cache.
  
  @​steelbrain in #​2003

v2.1.11

• Fixed an issue in getDataFromTree where queries that threw more than one
  error had error messages swallowed, and returned an invalid error object
  with circular references. Multiple errors are now preserved.
  
  @​anand-sundaram-zocdoc in #​2133
• Update both the <Mutation /> component and graphql HOC to accept a new
  awaitRefetchQueries prop (boo

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

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

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

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

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻️ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you check the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! Cannot read property 'match' of undefined

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2020-08-24T16_01_19_049Z-debug.log

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! Cannot read properties of undefined (reading 'match')

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-04-26T23_36_02_645Z-debug.log