fix(deps): update apollo graphql packages #2287

renovate · 2021-05-06T16:05:23Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@apollo/client (source)	`3.3.4` -> `3.7.10`
apollo-server	`2.19.0` -> `2.26.1`
apollo-server-express	`2.19.0` -> `2.26.1`
apollo-server-testing	`2.19.0` -> `2.25.3`
graphql-tag	`2.11.0` -> `2.12.6`

Release Notes

apollographql/apollo-client

`v3.7.10`

Compare Source

Patch Changes

#9438 52a9c8ea1 Thanks @dciesielkiewicz! - Ensure the client option passed to useMutation's execute function is used when provided. Previously this option was ignored.
#9124 975b923c0 Thanks @andrebrantom! - Make ApolloClient.writeQuery and ApolloClient.writeFragment behave more like cache.writeQuery and cache.writeFragment by returning the reference returned by the cache.

`v3.7.9`

Compare Source

Patch Changes

#10560 a561ecf43 Thanks @benjamn! - Keep __typename fragment when it does not contain @client directive and strip out inline fragments which use a @client directive. Thanks @Gazler and @mtsmfm!
#10560 251a12806 Thanks @benjamn! - Refactor removeDirectivesFromDocument to fix AST ordering sensitivities and avoid 1/3 AST traversals, potentially improving performance for large queries

`v3.7.8`

Compare Source

Patch Changes

#7555 45562d6fa Thanks @TheCeloReis! - Adds TVariables generic to GraphQLRequest and MockedResponse interfaces.
#10526 1d13de4f1 Thanks @benjamn! - Tolerate undefined concast.sources if complete called earlier than concast.start
#10497 8a883d8a1 Thanks @nevir! - Update SingleExecutionResult and IncrementalPayload's data types such that they no longer include undefined, which was not a valid runtime value, to fix errors when TypeScript's exactOptionalPropertyTypes is enabled.

`v3.7.7`

Compare Source

Patch Changes

#10502 315faf9ca Thanks @jerelmiller! - Log a warning to the console when a mock passed to MockedProvider or MockLink cannot be matched to a query during a test. This makes it easier to debug user errors in the mock setup, such as typos, especially if the query under test is using an errorPolicy set to ignore, which makes it difficult to know that a match did not occur.
#10499 9e54f5dfa Thanks @phryneas! - Allow the execution function returned by useLazyQuery to change the query.
#10362 14a56b105 Thanks @mccraveiro! - Fix error when server returns an error and we are also querying for a local field

`v3.7.6`

Compare Source

Patch Changes

#10470 47435e879 Thanks @alessbell! - Bumps TypeScript to 4.9.4 (previously 4.7.4) and updates types to account for changes in TypeScript 4.8 by propagating contstraints on generic types. Technically this makes some types stricter as attempting to pass null|undefined into certain functions is now disallowed by TypeScript, but these were never expected runtime values in the first place.
#10408 55ffafc58 Thanks @zlrlo! - fix: modify BatchHttpLink to have a separate timer for each different batch key
#9573 4a4f48dda Thanks @vladar! - Improve performance of local resolvers by only executing selection sets that contain an @client directive. Previously, local resolvers were executed even when the field did not contain @client. While the result was properly discarded, the unncessary work could negatively affect query performance, sometimes signficantly.

`v3.7.5`

Compare Source

Patch Changes

#10458 b5ccef229 Thanks @lennyburdette! - Passes getServerSnapshot to useSyncExternalStore so that it doesn't trigger a Missing getServerSnapshot error when using useFragment_experimental on the server.
#10471 895ddcb54 Thanks @alessbell! - More robust type definition for headers property passed to createHttpLink
#10321 bbaa3ef2d Thanks @alessbell! - Refetch should not return partial data with errorPolicy: none and notifyOnNetworkStatusChange: true.
#10402 0b07aa955 Thanks @Hugodby! - Improve context types
#10469 328c58f90 Thanks @jerelmiller! - Add generic type defaults when using useFragment to allow passing TData directly to the function without needing to specify TVars.

`v3.7.4`

Compare Source

Patch Changes

#10427 28d909cff Thanks @jerelmiller! - Ensure in-flight promises executed by useLazyQuery are rejected when useLazyQuery unmounts.
#10383 5c5ca9b01 Thanks @jerelmiller! - Ensure the onError callback is called when the errorPolicy is set to "all" and partial data is returned.
#10425 86e35a6d2 Thanks @jerelmiller! - Prefer the onError and onCompleted callback functions passed to the execute function returned from useMutation instead of calling both callback handlers.

`v3.7.3`

Compare Source

Patch Changes

#10334 7d923939d Thanks @jerelmiller! - Better handle deferred queries that have cached or partial cached data for them
#10368 46b58e976 Thanks @alessbell! - Fix: unblocks support for defer in mutations

If the @defer directive is present in the document passed to mutate, the Promise will resolve with the final merged data after the last multipart chunk has arrived in the response.

`v3.7.2`

Compare Source

Patch Changes

Only show dev tools suggestion in the console when connectToDevTools is true.

@chris110408 in #10258
Pass TCache generic to MutationHookOptions for better type support in useMutation.

@igrlk in #10223
Add name property to ApolloError to ensure better type safety and help error reporting tools better identify the error.

@aaronadamsCA in #9323
Export a ModifierDetails type for the details parameter of a Modifier function.

@KeithGillette in #7133
Revert use of cloneDeep to clone options when fetching queries.

@MrDoomBringer in #10215

`v3.7.1`

Compare Source

Patch Changes

#9438 52a9c8ea1 Thanks @dciesielkiewicz! - Ensure the client option passed to useMutation's execute function is used when provided. Previously this option was ignored.
#9124 975b923c0 Thanks @andrebrantom! - Make ApolloClient.writeQuery and ApolloClient.writeFragment behave more like cache.writeQuery and cache.writeFragment by returning the reference returned by the cache.

`v3.7.0`

Compare Source

Minor Changes

Implement preview support for the @defer directive.

@alessbell and @benjamn in #10018
Implement useFragment_experimental hook, which represents a lightweight live binding into the ApolloCache, and never triggers network requests of its own.

@benjamn in #8782
Allow registering named fragments with InMemoryCache to support using ...NamedFragment in queries without redeclaring NamedFragment repeatedly in every query that uses it.

@benjamn in #9764
Support onError callback for useSubscription hook.

@jeroenvisser101 in #9495
Implement preserveHeaderCase option for http context object, enabling preserved header capitalization for non-http-spec-compliant servers.

@mrdoombringer in #9891

Patch Changes

Delay calling onCompleted and onError callbacks passed to useQuery using Promise.resolve().then(() => ...) to fix issue #9794.

@dylanwulf in #9823
Replace concast.cleanup method with simpler concast.beforeNext API, which promises to call the given callback function just before the next result/error is delivered. In addition, concast.removeObserver no longer takes a quietly?: boolean parameter, since that parameter was partly responsible for cleanup callbacks sometimes not getting called.

@benjamn in #9718
Allow preserving header name capitalization when creating an HttpLink with createHttpLink({ uri, preserveHeaderCase: true }). Otherwise, header names are converted to lowercase to prevent case-sensitivity bugs.

@MrDoomBringer in #9891
Make queries with a pollInterval respect the no-cache fetch policy, instead of writing polled results into the cache.

@MrDoomBringer in #10020
Deprecate the onSubscriptionData callback in favor of a new onData callback for the useSubscription hook. Deprecate the onSubscriptionComplete callback in favor of a new onComplete callback for the useSubscription hook.

@jerelmiller in #10134

Potentially disruptive

The optional subscribeAndCount testing utility exported from @apollo/client/testing/core now takes a single generic TResult type parameter, instead of TData. This type will typically be inferred from the observable argument type, but if you have any explicit calls to subscribeAndCount<TData>(...) in your own codebase, you may need to adjust those calls accordingly.

@benjamn in #9718

`v3.6.10`

Compare Source

Improvements

The client options (variables, context, etc.) used for mutation calls are now available as the second argument to the onCompleted and onError callback functions.

@MrDoomBringer in #10052

`v3.6.9`

Compare Source

Bug Fixes

Leave fetchPolicy unchanged when skip: true (or in standby) and nextFetchPolicy is available, even if variables change.

@benjamn in #9823

`v3.6.8`

Compare Source

Bug Fixes

Fix incorrect variables passed in FieldFunctionOptions for nested readField calls in read and merge functions.

@stardustxx in #9808
Improve repository build scripts to work better on Windows.

@dylanwulf in #9805
Ensure useQuery(query, { skip: true }).called === false rather than always returning called as true.

@KucharskiPiotr in #9798
Allow abandoned reobserve requests to unsubscribe from their underlying Observable.

@javier-garcia-meteologica in #9791

`v3.6.7`

Compare Source

Bug Fixes

Fix regression (introduced in v3.6.0) that caused BatchHttpLink to discard pending batched queries on early completion of the underlying Observable.

@benjamn in #9793

`v3.6.6`

Compare Source

Bug Fixes

Allow useLazyQuery(query, { defaultOptions }) to benefit from defaultOptions.variables and client.defaultOptions.watchQuery.variables merging.

@benjamn in #9762

`v3.6.5`

Compare Source

Bug Fixes

Restore pre-v3.6 variables replacement behavior of ObservableQuery#reobserve method, fixing a regression that prevented removal of variables.

@benjamn in #9741
Preserve previousData even when different query or client provided to useQuery, instead of resetting previousData to undefined in those cases, matching behavior prior to v3.6.0.

@benjamn in #9734
Fix bug where onCompleted() and onError() are stale for useMutation().

@charle692 in #9740
Limit scope of DeepMerger object reuse, and avoid using Object.isFrozen, which can introduce differences between development and production if objects that were frozen using Object.freeze in development are left unfrozen in production.

@benjamn in #9742
Properly merge variables from original useLazyQuery(query, { variables }) with variables passed to execution function.

@benjamn in #9758

`v3.6.4`

Compare Source

Bug Fixes

Guarantee Concast cleanup without Observable cancelled prematurely rejection, potentially solving long-standing issues involving that error.

@benjamn in #9701
Ensure useSubscription subscriptions are properly restarted after unmounting/remounting by React 18 in <StrictMode>.

@kazekyo in #9707

Improvements

Internalize useSyncExternalStore shim, for more control than use-sync-external-store provides, fixing some React Native issues.

@benjamn in #9675 and #9709
Provide @apollo/client/**/*.cjs.native.js versions of every @apollo/client/**/*.cjs bundle (including dependencies ts-invariant and zen-observable-ts) to help React Native's Metro bundler automatically resolve CommonJS entry point modules. These changes should render unnecessary the advice we gave in the v3.5.4 section below about metro.config.js.

@benjamn in #9716
Handle falsy incoming data more gracefully in offetLimitPagination().merge function.

@shobhitsharma in #9705

`v3.6.3`

Compare Source

Bug Fixes

Simplify useQuery(query, { defaultOptions }) default options processing in order to fix bug where skip: true queries failed to execute upon switching to skip: false.

@benjamn in #9665
Add tests of skipping/unskipping and useLazyQuery with defaultOptions, and fix a bug causing duplicate requests.

@benjamn in #9666
Update ts-invariant to version 0.10.2 to fix source map warnings.

@benjamn in #9672
Test that useQuery queries with skip: true do not stall server-side rendering.

@nathanmarks and @benjamn in #9677
Prevent useLazyQuery from making duplicate requests when its execution function is first called, and stop rejecting the Promise it returns when result.error is defined.

@benjamn in #9684
Fix issue with useQuery returning loading: true state during server-side rendering with skip: true.

@nathanmarks in #9679

`v3.6.2`

Compare Source

Bug Fixes

Pass getServerSnapshot function to useSyncExternalStore in addition to getSnapshot, though the two functions behave identically. This change should fix/unbreak React 18 server rendering.

@hungphongbk in #9652

Improvements

Consider networkError.result.errors in addition to result.errors in PersistedQueryLink.

@redaid113 and @benjamn in #9410

`v3.6.1`

Compare Source

Improvements

The client options (variables, context, etc.) used for mutation calls are now available as the second argument to the onCompleted and onError callback functions.

@MrDoomBringer in #10052

`v3.6.0`

Compare Source

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/[email protected], 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

`v3.5.10`

Compare Source

Improvements

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.

@glasser in #9369

Note from @benjamn: since GraphQLWsLink is new functionality, we would normally wait for the next minor version (v3.6), but we were asked to expedite this release. These changes are strictly additive/opt-in/backwards-compatible, so shipping them in a patch release (3.5.10) seems safe, if unusual.

`v3.5.9`

Compare Source

Improvements

Interpret keyFields: [...] and keyArgs: [...] configurations in InMemoryCache type/field policies as ReadonlyArrays, since they are never mutated internally.

@julienfouilhe in #9339
Avoid declaring a global type for the __DEV__ constant, to avoid conflict with other such global declarations.

@benjamn in #9386

Bug Fixes

Fix useSubscription executing skipped subscription when input changes.

@levrik in #9299
Fix partial data appearing in useQuery().data when notifyOnNetworkStatusChange: true.

@brainkim in #9367
Prevent Promises returned by useLazyQuery execute functions from causing unhandled Promise rejection errors if uncaught.

@brainkim in #9380

`v3.5.8`

Compare Source

Bug Fixes

Fix the type of the called property returned by useQuery() and useLazyQuery().

@sztadii in #9304

Bug Fixes (by @brainkim in #9328)

Fix refetch() not being called when skip is true.
Fix the promise returned from the useLazyQuery() execution function having stale variables.
Fix the promise returned from the useLazyQuery() execution function not rejecting when a query errors.

`v3.5.7`

Compare Source

Bug Fixes

Fix regression that prevented calling onError or onCompleted in some cases when using useQuery.

@mmahalwy in #9226
Make useQuery respect defaultOptions.watchQuery.fetchPolicy.

@yasharzolmajdi in #9210

`v3.5.6`

Compare Source

Bug Fixes (by @brainkim in #9144)

Restores old behavior where the callback passed to useMutation() is constant.
Fix useMutation() callbacks having stale closures.
Fix useQuery() variables being out of date.

`v3.5.5`

Compare Source

Bug Fixes

Remove printer: Printer positional parameter from publicly-exported selectHttpOptionsAndBody function, whose addition in #8699 was a breaking change (starting in Apollo Client 3.5.0) for direct consumers of selectHttpOptionsAndBody.

@benjamn in #9103

`v3.5.4`

Compare Source

Notices

⚠️ The following advice about metro.config.js should no longer be necessary, as of Apollo Client v3.6.4.

[Relevant if you use Apollo Client with React Native] Since Apollo Client v3.5.0, CommonJS bundles provided by @apollo/client use a .cjs file extension rather than .cjs.js, so Node.js won't interpret them as ECMAScript modules. While this change should be an implementation detail, it may cause problems for the Metro bundler used by React Native, whose resolver.sourceExts configuration does not include the cjs extension by default.

As a workaround until this issue is resolved, you can configure Metro to understand the .cjs file extension by creating a metro.config.js file in the root of your React Native project:
```
// NOTE: No longer necessary in @&#8203;apollo/[email protected]!
const { getDefaultConfig } = require("metro-config");
const { resolver: defaultResolver } = getDefaultConfig.getDefaultValues();
exports.resolver = {
  ...defaultResolver,
  sourceExts: [...defaultResolver.sourceExts, "cjs"],
};
```

Improvements

Restore the ability to pass onError() and onCompleted() to the mutation execution function.
@brainkim in #9076
Work around webpack 5 errors of the form
The request 'ts-invariant/process' failed to resolve only because it was resolved as fully specified
by ensuring import ... from 'ts-invariant/process' is internally written to import ... from 'ts-invariant/process/index.js'.

@benjamn in #9083

`v3.5.3`

Compare Source

Avoid rewriting non-relative imported module specifiers in config/rewriteModuleIds.ts script, thereby allowing bundlers to resolve those imports as they see fit.

@benjamn in #9073
Ensure only current file is matched when running VSCode debugger.

@eps1lon in #9050

`v3.5.2`

Compare Source

Fix useMutation execute function returning non-identical execution functions when passing similar options.

@brainkim in #9037

`v3.5.1`

Compare Source

Improvements

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.

@glasser in #9369

Note from @benjamn: since GraphQLWsLink is new functionality, we would normally wait for the next minor version (v3.6), but we were asked to expedite this release. These changes are strictly additive/opt-in/backwards-compatible, so shipping them in a patch release (3.5.10) seems safe, if unusual.

`v3.5.0`

Compare Source

Improvements

Add updateQuery and updateFragment methods to ApolloCache, simplifying common readQuery/writeQuery cache update patterns.

@wassim-k in #8382
Field directives and their arguments can now be included along with field argument names when using field policy keyArgs: [...] notation. For example, if you have a Query.feed field that takes an argument called type and uses a @connection(key:...) directive to keep feed data from different queries separate within the cache, you might configure both using the following InMemoryCache field policy:
```
new InMemoryCache({
  typePolicies: {
    Query: {
      fields: {
        feed: {
          keyArgs: ["type", "@&#8203;connection", ["key"]],
        },
      },
    },
  },
});
```
@benjamn in #8678
Report single MissingFieldError instead of a potentially very large MissingFieldError[] array for incomplete cache reads, improving performance and memory usage.

@benjamn in #8734
When writing results into InMemoryCache, each written object is now identified using policies.identify after traversing the fields of the object (rather than before), simplifying identification and reducing duplicate work. If you have custom keyFields functions, they still receive the raw result object as their first parameter, but the KeyFieldsContext parameter now provides context.storeObject (the StoreObject just processed by processSelectionSet) and context.readField (a helper function for reading fields from context.storeObject and any References it might contain, similar to readField for read, merge, and cache.modify functions).

@benjamn in #8996
Ensure cache.identify never throws when primary key fields are missing, and include the source object in the error message when keyFields processing fails.

@benjamn in #8679
The HttpLink constructor now accepts an optional print function that can be used to customize how GraphQL DocumentNode objects are transformed back into strings before they are sent over the network.

@sarahgp in #8699
Make @apollo/client/testing a fully-fledged, independent entry point, instead of re-exporting @apollo/client/utilities/testing (which was never an entry point and no longer exists).

@benjamn in #8769
A new nested entry point called @apollo/client/testing/core has been created. Importing from this entry point instead of @apollo/client/testing excludes any React-related dependencies.

@wassim-k in #8687
Make cache.batch return the result of calling the options.update function.

@benjamn in #8696
The NetworkError and ErrorResponse types have been changed to align more closely.

@korywka in #8424
Include graphql@16 in peer deps.

@brainkim in #8997
Update zen-observable-ts to eliminate transitive dependency on @types/zen-observable.

@benjamn in #8695

React Refactoring

Improvements (due to @brainkim in #8875):

The useLazyQuery function now returns a promise with the result.
The useMutation result now exposes a method which can be reset.

Bug Fixes (due to @brainkim in #8596):

The useQuery and useLazyQuery hooks will now have ObservableQuery methods defined consistently.
Calling useLazyQuery methods like startPolling will start the query.
Calling the useLazyQuery execution function will now behave more like refetch. previousData will be preserved.
standby fetchPolicies will now act like skip: true more consistently.
Calling refetch on a skipped query will have no effect (issue #8270).
Prevent onError and onCompleted functions from firing continuously, and improving their polling behavior.

`v3.4.17`

Compare Source

Improvements

Allow TOptions extends FieldFunctionOptions to be passed as final (optional) type parameter of FieldPolicy type.

@VictorGaiva in #9000

`v3.4.16`

Compare Source

Improvements

Prevent webpack from misresolving the graphql package as the local @apollo/client/utilities/globals/graphql.js module when module.exports.resolve.preferRelative is enabled in webpack.config.js.

Note: if you encounter strange module resolution errors like export 'isType' (imported as 'isType') was not found in 'graphql' (possible exports: removeTemporaryGlobals) please try removing preferRelative: true from your webpack.config.js file, or find a way to disable that resolution behavior for packages within node_modules.

@benjamn in #8862
Avoid importing isType from the graphql package internally, to prevent bundlers from including as much as 3.4kB of unnecessary code.

@benjamn in #8891
Make client.resetStore and client.clearStore pass appropriate discardWatches option to cache.reset.

@benjamn in #8873

`v3.4.15`

Compare Source

Bug Fixes

Require calling cache.reset({ discardWatches: true }) to make cache.reset discard cache.watches, restoring behavior broken in v3.4.14 by #8826.

@benjamn in #8852

`v3.4.14`

Compare Source

Bug Fixes

Disable InMemoryCache result object canonization by default, to prevent unexpected memory growth and/or reuse of object references, with multiple ways to reenable it (per-cache, per-query, or a mixture of both).

@benjamn in #8822
Clear InMemoryCache watches set when cache.reset() called.

@benjamn in #8826
Stop excluding observerless queries from refetchQueries: [...] selection.

@benjamn in #8825
Prevent optimistic cache evictions from evicting non-optimistic data.

@benjamn in #8829
Ensure cache.broadcastWatch passes all relevant WatchOptions to cache.diff as DiffOptions.

@benjamn in #8832

`v3.4.13`

Compare Source

Bug Fixes

Fix componentDidUpate typo in withSubscription higher-order component.

@YarBez in #7506
Fix internal canUseSymbol import within @apollo/client/utilities to avoid breaking bundlers/builds.

@benjamn in #8817
Tolerate unfreezable objects like Uint8Array and Buffer in maybeDeepFreeze.

@geekuillaume and @benjamn in #8813

`v3.4.12`

Compare Source

Bug Fixes

Improve handling of falsy existing and/or incoming parameters in relayStylePagination field policy helper function.

[@bubba](https://togit

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 bot force-pushed the renovate/apollo-graphql-packages branch 2 times, most recently from 1fda37e to fdc07d0 Compare May 13, 2021 16:35

renovate bot force-pushed the renovate/apollo-graphql-packages branch 2 times, most recently from edc176d to f4db127 Compare May 18, 2021 23:46

renovate bot force-pushed the renovate/apollo-graphql-packages branch from f4db127 to 00aa5f8 Compare May 27, 2021 16:07

renovate bot force-pushed the renovate/apollo-graphql-packages branch 3 times, most recently from 8fd9dfb to bfcaed7 Compare June 8, 2021 23:22

renovate bot force-pushed the renovate/apollo-graphql-packages branch 2 times, most recently from 281b8fa to 444b170 Compare June 25, 2021 17:19

renovate bot force-pushed the renovate/apollo-graphql-packages branch from 444b170 to 5048425 Compare October 18, 2021 16:09

renovate bot force-pushed the renovate/apollo-graphql-packages branch from 5048425 to 73cd911 Compare March 7, 2022 10:30

renovate bot force-pushed the renovate/apollo-graphql-packages branch from 73cd911 to 8964b82 Compare May 16, 2022 02:05

renovate bot force-pushed the renovate/apollo-graphql-packages branch 2 times, most recently from b3ba182 to b843f19 Compare June 22, 2022 22:50

renovate bot changed the title ~~fix(deps): update apollo graphql packages~~ fix(deps): update Apollo GraphQL packages Jun 27, 2022

renovate bot changed the title ~~fix(deps): update Apollo GraphQL packages~~ fix(deps): update apollo graphql packages Jun 28, 2022

renovate bot force-pushed the renovate/apollo-graphql-packages branch from b843f19 to 4adfd6d Compare September 25, 2022 15:59

renovate bot force-pushed the renovate/apollo-graphql-packages branch from 4adfd6d to 35633f6 Compare November 20, 2022 20:22

renovate bot force-pushed the renovate/apollo-graphql-packages branch from 35633f6 to 86b0601 Compare March 16, 2023 07:07

renovate bot force-pushed the renovate/apollo-graphql-packages branch from 86b0601 to 5942f77 Compare March 31, 2023 19:21

fix(deps): update apollo graphql packages

87b594f

renovate bot force-pushed the renovate/apollo-graphql-packages branch from 5942f77 to 87b594f Compare April 17, 2023 09:55

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(deps): update apollo graphql packages #2287

fix(deps): update apollo graphql packages #2287

renovate bot commented May 6, 2021 •

edited

Loading

fix(deps): update apollo graphql packages #2287

Are you sure you want to change the base?

fix(deps): update apollo graphql packages #2287

Conversation

renovate bot commented May 6, 2021 • edited Loading

Release Notes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Potentially disruptive

Improvements

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Improvements

Bug Fixes

Bug Fixes

Improvements

Improvements

Potentially disruptive changes

React 18

Improvements

Improvements

Improvements

Bug Fixes

Bug Fixes

Bug Fixes (by @​brainkim in #​9328)

Bug Fixes

Bug Fixes (by @​brainkim in #​9144)

Bug Fixes

Notices

Improvements

Improvements

Improvements

React Refactoring

Improvements (due to @​brainkim in #​8875):

Bug Fixes (due to @​brainkim in #​8596):

Improvements

Improvements

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Configuration

renovate bot commented May 6, 2021 •

edited

Loading

Bug Fixes (by @brainkim in #9328)

Bug Fixes (by @brainkim in #9144)

Improvements (due to @brainkim in #8875):

Bug Fixes (due to @brainkim in #8596):