search

keystonejs / keystone-5

https://v5.keystonejs.com
MIT License
64 stars 33 forks source link

Update Apollo GraphQL packages (minor) #311

Closed renovate[bot] closed 2 years ago

renovate[bot] commented 3 years ago

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@apollo/client (source) ^3.3.20 -> ^3.5.6 age adoption passing confidence
apollo-server-express ^2.23.0 -> ^2.25.3 age adoption passing confidence
graphql-tag ^2.11.0 -> ^2.12.6 age adoption passing confidence

Release Notes

apollographql/apollo-client ### [`v3.5.6`](https://togithub.com/apollographql/apollo-client/blob/HEAD/CHANGELOG.md#Apollo-Client-356-2021-12-07) [Compare Source](https://togithub.com/apollographql/apollo-client/compare/v3.5.5...v3.5.6) ##### Bug Fixes (by [@​brainkim](https://togithub.com/brainkim) in [#​9144](https://togithub.com/apollographql/apollo-client/pull/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`](https://togithub.com/apollographql/apollo-client/blob/HEAD/CHANGELOG.md#Apollo-Client-355-2021-11-23) [Compare Source](https://togithub.com/apollographql/apollo-client/compare/v3.5.4...v3.5.5) ##### Bug Fixes - Remove `printer: Printer` positional parameter from publicly-exported `selectHttpOptionsAndBody` function, whose addition in [#​8699](https://togithub.com/apollographql/apollo-client/pull/8699) was a breaking change (starting in Apollo Client 3.5.0) for direct consumers of `selectHttpOptionsAndBody`.
[@​benjamn](https://togithub.com/benjamn) in [#​9103](https://togithub.com/apollographql/apollo-client/pull/9103) ### [`v3.5.4`](https://togithub.com/apollographql/apollo-client/blob/HEAD/CHANGELOG.md#Apollo-Client-354-2021-11-19) [Compare Source](https://togithub.com/apollographql/apollo-client/compare/v3.5.3...v3.5.4) ##### Notices - \[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](https://facebook.github.io/metro/) used by React Native, whose [`resolver.sourceExts`](https://facebook.github.io/metro/docs/configuration#sourceexts) configuration does not include the `cjs` extension by default. As a workaround until [this issue](https://togithub.com/facebook/metro/issues/535) 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: ```js 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](https://togithub.com/brainkim) in [#​9076](https://togithub.com/apollographql/apollo-client/pull/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](https://togithub.com/benjamn) in [#​9083](https://togithub.com/apollographql/apollo-client/pull/9083) ### [`v3.5.3`](https://togithub.com/apollographql/apollo-client/blob/HEAD/CHANGELOG.md#Apollo-Client-353-2021-11-17) [Compare Source](https://togithub.com/apollographql/apollo-client/compare/v3.5.2...v3.5.3) - Avoid rewriting non-relative imported module specifiers in `config/rewriteModuleIds.ts` script, thereby allowing bundlers to resolve those imports as they see fit.
[@​benjamn](https://togithub.com/benjamn) in [#​9073](https://togithub.com/apollographql/apollo-client/pull/9073) - Ensure only current file is matched when running VSCode debugger.
[@​eps1lon](https://togithub.com/eps1lon) in [#​9050](https://togithub.com/apollographql/apollo-client/pull/9050) ### [`v3.5.2`](https://togithub.com/apollographql/apollo-client/blob/HEAD/CHANGELOG.md#Apollo-Client-352-2021-11-10) [Compare Source](https://togithub.com/apollographql/apollo-client/compare/v3.5.1...v3.5.2) - Fix useMutation execute function returning non-identical execution functions when passing similar options.
[@​brainkim](https://togithub.com/brainkim) in [#​9093](https://togithub.com/apollographql/apollo-client/pull/9037) ### [`v3.5.1`](https://togithub.com/apollographql/apollo-client/blob/HEAD/CHANGELOG.md#Apollo-Client-351-2021-11-09) [Compare Source](https://togithub.com/apollographql/apollo-client/compare/v3.5.0...v3.5.1) - Remove npm from dependencies, and avoid referencing graphql-js enum value.
[@​brainkim](https://togithub.com/brainkim) in [#​9030](https://togithub.com/apollographql/apollo-client/pull/9030) ### [`v3.5.0`](https://togithub.com/apollographql/apollo-client/blob/HEAD/CHANGELOG.md#Apollo-Client-350-2021-11-08) [Compare Source](https://togithub.com/apollographql/apollo-client/compare/v3.4.17...v3.5.0) ##### Improvements - Add `updateQuery` and `updateFragment` methods to `ApolloCache`, simplifying common `readQuery`/`writeQuery` cache update patterns.
[@​wassim-k](https://togithub.com/wassim-k) in [#​8382](https://togithub.com/apollographql/apollo-client/pull/8382) - Field directives and their arguments can now be included along with field argument names when using [field policy `keyArgs: [...]` notation](https://www.apollographql.com/docs/react/pagination/key-args/). 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: ```ts new InMemoryCache({ typePolicies: { Query: { fields: { feed: { keyArgs: ["type", "@​connection", ["key"]], }, }, }, }, }) ``` [@​benjamn](https://togithub.com/benjamn) in [#​8678](https://togithub.com/apollographql/apollo-client/pull/8678) - Report single `MissingFieldError` instead of a potentially very large `MissingFieldError[]` array for incomplete cache reads, improving performance and memory usage.
[@​benjamn](https://togithub.com/benjamn) in [#​8734](https://togithub.com/apollographql/apollo-client/pull/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 `Reference`s it might contain, similar to `readField` for `read`, `merge`, and `cache.modify` functions).
[@​benjamn](https://togithub.com/benjamn) in [#​8996](https://togithub.com/apollographql/apollo-client/pull/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](https://togithub.com/benjamn) in [#​8679](https://togithub.com/apollographql/apollo-client/pull/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](https://togithub.com/sarahgp) in [#​8699](https://togithub.com/apollographql/apollo-client/pull/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](https://togithub.com/benjamn) in [#​8769](https://togithub.com/apollographql/apollo-client/pull/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](https://togithub.com/wassim-k) in [#​8687](https://togithub.com/apollographql/apollo-client/pull/8687) - Make `cache.batch` return the result of calling the `options.update` function.
[@​benjamn](https://togithub.com/benjamn) in [#​8696](https://togithub.com/apollographql/apollo-client/pull/8696) - The `NetworkError` and `ErrorResponse` types have been changed to align more closely.
[@​korywka](https://togithub.com/korywka) in [#​8424](https://togithub.com/apollographql/apollo-client/pull/8424) - Include `graphql@16` in peer deps.
[@​brainkim](https://togithub.com/brainkim) in [#​8997](https://togithub.com/apollographql/apollo-client/pull/8997) - Update `zen-observable-ts` to eliminate transitive dependency on `@types/zen-observable`.
[@​benjamn](https://togithub.com/benjamn) in [#​8695](https://togithub.com/apollographql/apollo-client/pull/8695) ##### React Refactoring ##### Improvements (due to [@​brainkim](https://togithub.com/brainkim) in [#​8875](https://togithub.com/apollographql/apollo-client/pull/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](https://togithub.com/brainkim) in [#​8596](https://togithub.com/apollographql/apollo-client/pull/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](https://togithub.com/apollographql/apollo-client/issues/8270)). - Prevent `onError` and `onCompleted` functions from firing continuously, and improving their polling behavior. ### [`v3.4.17`](https://togithub.com/apollographql/apollo-client/blob/HEAD/CHANGELOG.md#Apollo-Client-3417-2021-11-08) [Compare Source](https://togithub.com/apollographql/apollo-client/compare/v3.4.16...v3.4.17) ##### Improvements - Allow `TOptions extends FieldFunctionOptions` to be passed as final (optional) type parameter of `FieldPolicy` type.
[@​VictorGaiva](https://togithub.com/VictorGaiva) in [#​9000](https://togithub.com/apollographql/apollo-client/pull/9000) ### [`v3.4.16`](https://togithub.com/apollographql/apollo-client/blob/HEAD/CHANGELOG.md#Apollo-Client-3416) [Compare Source](https://togithub.com/apollographql/apollo-client/compare/v3.4.15...v3.4.16) ##### 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](https://togithub.com/benjamn) in [#​8862](https://togithub.com/apollographql/apollo-client/pull/8862) - Avoid importing `isType` from the `graphql` package internally, to prevent bundlers from including as much as 3.4kB of unnecessary code.
[@​benjamn](https://togithub.com/benjamn) in [#​8891](https://togithub.com/apollographql/apollo-client/pull/8891) - Make `client.resetStore` and `client.clearStore` pass appropriate `discardWatches` option to `cache.reset`.
[@​benjamn](https://togithub.com/benjamn) in [#​8873](https://togithub.com/apollographql/apollo-client/pull/8873) ### [`v3.4.15`](https://togithub.com/apollographql/apollo-client/blob/HEAD/CHANGELOG.md#Apollo-Client-3415) [Compare Source](https://togithub.com/apollographql/apollo-client/compare/v3.4.14...v3.4.15) ##### Bug Fixes - Require calling `cache.reset({ discardWatches: true })` to make `cache.reset` discard `cache.watches`, restoring behavior broken in v3.4.14 by [#​8826](https://togithub.com/apollographql/apollo-client/pull/8826).
[@​benjamn](https://togithub.com/benjamn) in [#​8852](https://togithub.com/apollographql/apollo-client/pull/8852) ### [`v3.4.14`](https://togithub.com/apollographql/apollo-client/blob/HEAD/CHANGELOG.md#Apollo-Client-3414) [Compare Source](https://togithub.com/apollographql/apollo-client/compare/v3.4.13...v3.4.14) ##### Bug Fixes - Disable `InMemoryCache` [result object canonization](https://togithub.com/apollographql/apollo-client/pull/7439) 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](https://togithub.com/benjamn) in [#​8822](https://togithub.com/apollographql/apollo-client/pull/8822) - Clear `InMemoryCache` `watches` set when `cache.reset()` called.
[@​benjamn](https://togithub.com/benjamn) in [#​8826](https://togithub.com/apollographql/apollo-client/pull/8826) - Stop excluding observerless queries from `refetchQueries: [...]` selection.
[@​benjamn](https://togithub.com/benjamn) in [#​8825](https://togithub.com/apollographql/apollo-client/pull/8825) - Prevent optimistic cache evictions from evicting non-optimistic data.
[@​benjamn](https://togithub.com/benjamn) in [#​8829](https://togithub.com/apollographql/apollo-client/pull/8829) - Ensure `cache.broadcastWatch` passes all relevant `WatchOptions` to `cache.diff` as `DiffOptions`.
[@​benjamn](https://togithub.com/benjamn) in [#​8832](https://togithub.com/apollographql/apollo-client/pull/8832) ### [`v3.4.13`](https://togithub.com/apollographql/apollo-client/blob/HEAD/CHANGELOG.md#Apollo-Client-3413) [Compare Source](https://togithub.com/apollographql/apollo-client/compare/v3.4.12...v3.4.13) ##### Bug Fixes - Fix `componentDidUpate` typo in `withSubscription` higher-order component.
[@​YarBez](https://togithub.com/YarBez) in [#​7506](https://togithub.com/apollographql/apollo-client/pull/7506) - Fix internal `canUseSymbol` import within `@apollo/client/utilities` to avoid breaking bundlers/builds.
[@​benjamn](https://togithub.com/benjamn) in [#​8817](https://togithub.com/apollographql/apollo-client/pull/8817) - Tolerate unfreezable objects like `Uint8Array` and `Buffer` in `maybeDeepFreeze`.
[@​geekuillaume](https://togithub.com/geekuillaume) and [@​benjamn](https://togithub.com/benjamn) in [#​8813](https://togithub.com/apollographql/apollo-client/pull/8813) ### [`v3.4.12`](https://togithub.com/apollographql/apollo-client/blob/HEAD/CHANGELOG.md#Apollo-Client-3412) [Compare Source](https://togithub.com/apollographql/apollo-client/compare/v3.4.11...v3.4.12) ##### Bug Fixes - Improve handling of falsy `existing` and/or `incoming` parameters in `relayStylePagination` field policy helper function.
[@​bubba](https://togithub.com/bubba) and [@​benjamn](https://togithub.com/benjamn) in [#​8733](https://togithub.com/apollographql/apollo-client/pull/8733) - Associate Apollo context with `React.createContext` (instead of using a local `WeakMap`) again, so multiple copies of `@apollo/client` (uncommon) can share the same context.
[@​benjamn](https://togithub.com/benjamn) in [#​8798](https://togithub.com/apollographql/apollo-client/pull/8798) ### [`v3.4.11`](https://togithub.com/apollographql/apollo-client/blob/HEAD/CHANGELOG.md#Apollo-Client-3411) [Compare Source](https://togithub.com/apollographql/apollo-client/compare/v3.4.10...v3.4.11) ##### Bug Fixes - Fix [Vite](https://vitejs.dev) tree-shaking by calling the `checkDEV()` function (at least once) in the module that exports it, `@apollo/client/utilities/globals/index.ts`.
[@​benjamn](https://togithub.com/benjamn) in [#​8767](https://togithub.com/apollographql/apollo-client/pull/8767) ##### Improvements - Export `PersistedQueryLink` namespace from `@apollo/client/link/persisted-queries`.
[@​vedrani](https://togithub.com/vedrani) in [#​8761](https://togithub.com/apollographql/apollo-client/pull/8761) ##### Documentation - Upgrade docs theme for new Algolia-powered search experience.
[@​trevorblades](https://togithub.com/trevorblades) in [#​8768](https://togithub.com/apollographql/apollo-client/pull/8768) ### [`v3.4.10`](https://togithub.com/apollographql/apollo-client/blob/HEAD/CHANGELOG.md#Apollo-Client-3410) [Compare Source](https://togithub.com/apollographql/apollo-client/compare/v3.4.9...v3.4.10) ##### Improvements - Warn when calling `refetch({ variables })` instead of `refetch(variables)`, except for queries that declare a variable named `$variables` (uncommon).
[@​benjamn](https://togithub.com/benjamn) in [#​8702](https://togithub.com/apollographql/apollo-client/pull/8702) ##### Bug Fixes - Fix `ObservableQuery.getCurrentResult()` returning cached `data` with certain fetch policies.
[@​brainkim](https://togithub.com/brainkim) in [#​8718](https://togithub.com/apollographql/apollo-client/pull/8718) - Prevent `ssrMode`/`ssrForceFetchDelay` from causing queries to hang.
[@​brainkim](https://togithub.com/brainkim) in [#​8709](https://togithub.com/apollographql/apollo-client/pull/8709) - Import `@apollo/client/utilities/globals` internally wherever `__DEV__` is used, not just in `@apollo/client/**/index.js` entry points.
[@​benjamn](https://togithub.com/benjamn) in [#​8720](https://togithub.com/apollographql/apollo-client/pull/8720) ### [`v3.4.9`](https://togithub.com/apollographql/apollo-client/blob/HEAD/CHANGELOG.md#Apollo-Client-349) [Compare Source](https://togithub.com/apollographql/apollo-client/compare/v3.4.8...v3.4.9) ##### Bug Fixes - Fix unhandled `Promise` rejection warnings/errors whose message is `Observable cancelled prematurely`.
[@​benjamn](https://togithub.com/benjamn) in [#​8676](https://togithub.com/apollographql/apollo-client/pull/8676) - Enforce that `__DEV__` is polyfilled by every `@apollo/client/*` entry point that uses it. This build step considers not only explicit `__DEV__` usage but also `__DEV__` references injected near `invariant(...)` and `new InvariantError(...)` expressions.
[@​benjamn](https://togithub.com/benjamn) in [#​8689](https://togithub.com/apollographql/apollo-client/pull/8689) ### [`v3.4.8`](https://togithub.com/apollographql/apollo-client/blob/HEAD/CHANGELOG.md#Apollo-Client-348) [Compare Source](https://togithub.com/apollographql/apollo-client/compare/v3.4.7...v3.4.8) ##### Bug Fixes - Fix error thrown by nested `keyFields: ["a", ["b", "c"], "d"]` type policies when writing results into the cache where any of the key fields (`.a`, `.a.b`, `.a.c`, or `.d`) have been renamed by query field alias syntax.
[@​benjamn](https://togithub.com/benjamn) in [#​8643](https://togithub.com/apollographql/apollo-client/pull/8643) - Fix regression from PR [#​8422](https://togithub.com/apollographql/apollo-client/pull/8422) (first released in `@apollo/client@3.4.0-rc.15`) that caused `result.data` to be set to undefined in some cases after `ObservableQuery#getCurrentResult` reads an incomplete result from the cache.
[@​benjamn](https://togithub.com/benjamn) in [#​8642](https://togithub.com/apollographql/apollo-client/pull/8642) ### [`v3.4.7`](https://togithub.com/apollographql/apollo-client/blob/HEAD/CHANGELOG.md#Apollo-Client-347) [Compare Source](https://togithub.com/apollographql/apollo-client/compare/v3.4.6...v3.4.7) ##### Bug Fixes - Fix accidental reuse of recycled `MergeTree` objects in `StoreWriter` class used by `InMemoryCache`.
[@​benjamn](https://togithub.com/benjamn) in [#​8618](https://togithub.com/apollographql/apollo-client/pull/8618) ### [`v3.4.6`](https://togithub.com/apollographql/apollo-client/blob/HEAD/CHANGELOG.md#Apollo-Client-346) [Compare Source](https://togithub.com/apollographql/apollo-client/compare/v3.4.5...v3.4.6) ##### Improvements - Reevaluate `window.fetch` each time `HttpLink` uses it, if not configured using `options.fetch`. This change enables a variety of strategies for instrumenting `window.fetch`, without requiring those strategies to run before `@apollo/client/link/http` is first imported.
[@​benjamn](https://togithub.com/benjamn) in [#​8603](https://togithub.com/apollographql/apollo-client/pull/8603) - Clarify mutation `fetchPolicy` options (`"network-only"` or `"no-cache"`) using [`MutationFetchPolicy`](https://togithub.com/apollographql/apollo-client/blob/fa52875341ab33f3e8192ded90af5e2c208e0f75/src/core/watchQueryOptions.ts#L33-L37) union type.
[@​benjamn](https://togithub.com/benjamn) in [#​8602](https://togithub.com/apollographql/apollo-client/pull/8602) ##### Bug Fixes - Restore full `@apollo/client/apollo-client.cjs.js` CommonJS bundle for older bundlers. > Note that Node.js and CommonJS bundlers typically use the bundles specified by `"main"` fields in our generated `package.json` files, which are all independent and non-overlapping CommonJS modules. However, `apollo-client.cjs.js` is just one big bundle, so mixing imports of `apollo-client.cjs.js` with the other CommonJS bundles is discouraged, as it could trigger the [dual package hazard](https://nodejs.org/api/packages.html#packages_dual_commonjs_es_module_packages). In other words, please don't start using `apollo-client.cjs.js` if you're not already.
[@​benjamn](https://togithub.com/benjamn) in [#​8592](https://togithub.com/apollographql/apollo-client/pull/8592) - Log `MissingFieldError`s in `ObservableQuery#getCurrentResult` using `invariant.debug`, rather than reporting them via `result.error`.
[@​benjamn](https://togithub.com/benjamn) in [#​8604](https://togithub.com/apollographql/apollo-client/pull/8604) ### [`v3.4.5`](https://togithub.com/apollographql/apollo-client/blob/HEAD/CHANGELOG.md#Apollo-Client-345) [Compare Source](https://togithub.com/apollographql/apollo-client/compare/v3.4.4...v3.4.5) ##### Bug Fixes - Fix double registration bug for mutation `refetchQueries` specified using legacy one-time `refetchQueries: [{ query, variables }]` style. Though the bug is fixed, we recommend using `refetchQueries: [query]` instead (when possible) to refetch an existing query using its `DocumentNode`, rather than creating, executing, and then deleting a new query, as the legacy `{ query, variables }` style unfortunately does.
[@​benjamn](https://togithub.com/benjamn) in [#​8586](https://togithub.com/apollographql/apollo-client/pull/8586) - Fix `useQuery`/`useLazyQuery` stalling when clients or queries change.
[@​brainkim](https://togithub.com/brainkim) in [#​8589](https://togithub.com/apollographql/apollo-client/pull/8589) ### [`v3.4.4`](https://togithub.com/apollographql/apollo-client/blob/HEAD/CHANGELOG.md#Apollo-Client-344) [Compare Source](https://togithub.com/apollographql/apollo-client/compare/v3.4.3...v3.4.4) ##### Bug Fixes - Revert accidental addition of `engines.npm` section to published version of `@apollo/client/package.json`.
[@​benjamn](https://togithub.com/benjamn) in [#​8578](https://togithub.com/apollographql/apollo-client/pull/8578) ### [`v3.4.3`](https://togithub.com/apollographql/apollo-client/blob/HEAD/CHANGELOG.md#Apollo-Client-343) [Compare Source](https://togithub.com/apollographql/apollo-client/compare/v3.4.2...v3.4.3) ##### Bug Fixes - Fix `{ ssr: false }` causing queries to hang on the client.
[@​brainkim](https://togithub.com/brainkim) in [#​8574](https://togithub.com/apollographql/apollo-client/pull/8574) ### [`v3.4.2`](https://togithub.com/apollographql/apollo-client/blob/HEAD/CHANGELOG.md#Apollo-Client-342) [Compare Source](https://togithub.com/apollographql/apollo-client/compare/v3.4.1...v3.4.2) ##### Bug Fixes - Use more default type parameters for mutation-related types in `react/types/types.ts`, to provide smoother backwards compatibility for code using those types explicitly.
[@​benjamn](https://togithub.com/benjamn) in [#​8573](https://togithub.com/apollographql/apollo-client/pull/8573) ### [`v3.4.1`](https://togithub.com/apollographql/apollo-client/blob/HEAD/CHANGELOG.md#Apollo-Client-3417-2021-11-08) [Compare Source](https://togithub.com/apollographql/apollo-client/compare/v3.4.0...v3.4.1) ##### Improvements - Allow `TOptions extends FieldFunctionOptions` to be passed as final (optional) type parameter of `FieldPolicy` type.
[@​VictorGaiva](https://togithub.com/VictorGaiva) in [#​9000](https://togithub.com/apollographql/apollo-client/pull/9000) ### [`v3.4.0`](https://togithub.com/apollographql/apollo-client/blob/HEAD/CHANGELOG.md#Apollo-Client-340) [Compare Source](https://togithub.com/apollographql/apollo-client/compare/v3.3.21...v3.4.0) ##### New documentation - [**Refetching queries**](https://www.apollographql.com/docs/react/data/refetching/) with `client.refetchQueries`.
[@​StephenBarlow](https://togithub.com/StephenBarlow) and [@​benjamn](https://togithub.com/benjamn) in [#​8265](https://togithub.com/apollographql/apollo-client/pull/8265) ##### Improvements - `InMemoryCache` now *guarantees* that any two result objects returned by the cache (from `readQuery`, `readFragment`, etc.) will be referentially equal (`===`) if they are deeply equal. Previously, `===` equality was often achievable for results for the same query, on a best-effort basis. Now, equivalent result objects will be automatically shared among the result trees of completely different queries. This guarantee is important for taking full advantage of optimistic updates that correctly guess the final data, and for "pure" UI components that can skip re-rendering when their input data are unchanged.
[@​benjamn](https://togithub.com/benjamn) in [#​7439](https://togithub.com/apollographql/apollo-client/pull/7439) - Mutations now accept an optional callback function called `onQueryUpdated`, which will be passed the `ObservableQuery` and `Cache.DiffResult` objects for any queries invalidated by cache writes performed by the mutation's final `update` function. Using `onQueryUpdated`, you can override the default `FetchPolicy` of the query, by (for example) calling `ObservableQuery` methods like `refetch` to force a network request. This automatic detection of invalidated queries provides an alternative to manually enumerating queries using the `refetchQueries` mutation option. Also, if you return a `Promise` from `onQueryUpdated`, the mutation will automatically await that `Promise`, rendering the `awaitRefetchQueries` option unnecessary.
[@​benjamn](https://togithub.com/benjamn) in [#​7827](https://togithub.com/apollographql/apollo-client/pull/7827) - Support `client.refetchQueries` as an imperative way to refetch queries, without having to pass `options.refetchQueries` to `client.mutate`.
[@​dannycochran](https://togithub.com/dannycochran) in [#​7431](https://togithub.com/apollographql/apollo-client/pull/7431) - Improve standalone `client.refetchQueries` method to support automatic detection of queries needing to be refetched.
[@​benjamn](https://togithub.com/benjamn) in [#​8000](https://togithub.com/apollographql/apollo-client/pull/8000) - Fix remaining barriers to loading [`@apollo/client/core`](https://cdn.jsdelivr.net/npm/@​apollo/client@3.4.0/core/+esm) as native ECMAScript modules from a CDN like [esm.run](https://www.jsdelivr.com/esm). Importing `@apollo/client` from a CDN will become possible once we move all React-related dependencies into `@apollo/client/react` in Apollo Client 4.
[@​benjamn](https://togithub.com/benjamn) in [#​8266](https://togithub.com/apollographql/apollo-client/issues/8266) - `InMemoryCache` supports a new method called `batch`, which is similar to `performTransaction` but takes named options rather than positional parameters. One of these named options is an `onDirty(watch, diff)` callback, which can be used to determine which watched queries were invalidated by the `batch` operation.
[@​benjamn](https://togithub.com/benjamn) in [#​7819](https://togithub.com/apollographql/apollo-client/pull/7819) - Allow `merge: true` field policy to merge `Reference` objects with non-normalized objects, and vice-versa.
[@​benjamn](https://togithub.com/benjamn) in [#​7778](https://togithub.com/apollographql/apollo-client/pull/7778) - Allow identical subscriptions to be deduplicated by default, like queries.
[@​jkossis](https://togithub.com/jkossis) in [#​6910](https://togithub.com/apollographql/apollo-client/pull/6910) - Always use `POST` request when falling back to sending full query with `@apollo/client/link/persisted-queries`.
[@​rieset](https://togithub.com/rieset) in [#​7456](https://togithub.com/apollographql/apollo-client/pull/7456) - The `FetchMoreQueryOptions` type now takes two instead of three type parameters (``), thanks to using `Partial` instead of `K extends typeof TVariables` and `Pick`.
[@​ArnaudBarre](https://togithub.com/ArnaudBarre) in [#​7476](https://togithub.com/apollographql/apollo-client/pull/7476) - Pass `variables` and `context` to a mutation's `update` function. **Note:** The type of the `update` function is now named `MutationUpdaterFunction` rather than `MutationUpdaterFn`, since the older type was [broken beyond repair](https://togithub.com/apollographql/apollo-client/issues/8506#issuecomment-881706613). If you are using `MutationUpdaterFn` in your own code, please use `MutationUpdaterFunction` instead.
[@​jcreighton](https://togithub.com/jcreighton) in [#​7902](https://togithub.com/apollographql/apollo-client/pull/7902) - A `resultCacheMaxSize` option may be passed to the `InMemoryCache` constructor to limit the number of result objects that will be retained in memory (to speed up repeated reads), and calling `cache.reset()` now releases all such memory.
[@​SofianHn](https://togithub.com/SofianHn) in [#​8107](https://togithub.com/apollographql/apollo-client/pull/8107) - Fully remove result cache entries from LRU dependency system when the corresponding entities are removed from `InMemoryCache` by eviction, or by any other means.
[@​sofianhn](https://togithub.com/sofianhn) and [@​benjamn](https://togithub.com/benjamn) in [#​8147](https://togithub.com/apollographql/apollo-client/pull/8147) - Expose missing field errors in results.
[@​brainkim](github.com/brainkim) in [#​8262](https://togithub.com/apollographql/apollo-client/pull/8262) - Add expected/received `variables` to `No more mocked responses...` error messages generated by `MockLink`.
[@​markneub](github.com/markneub) in [#​8340](https://togithub.com/apollographql/apollo-client/pull/8340) - The `InMemoryCache` version of the `cache.gc` method now supports additional options for removing non-essential (recomputable) result caching data.
[@​benjamn](https://togithub.com/benjamn) in [#​8421](https://togithub.com/apollographql/apollo-client/pull/8421) - Suppress noisy `Missing cache result fields...` warnings by default unless `setLogVerbosity("debug")` called.
[@​benjamn](https://togithub.com/benjamn) in [#​8489](https://togithub.com/apollographql/apollo-client/pull/8489) - Improve interaction between React hooks and React Fast Refresh in development.
[@​andreialecu](https://togithub.com/andreialecu) in [#​7952](https://togithub.com/apollographql/apollo-client/pull/7952) ##### Potentially disruptive changes - To avoid retaining sensitive information from mutation root field arguments, Apollo Client v3.4 automatically clears any `ROOT_MUTATION` fields from the cache after each mutation finishes. If you need this information to remain in the cache, you can prevent the removal by passing the `keepRootFields: true` option to `client.mutate`. `ROOT_MUTATION` result data are also passed to the mutation `update` function, so we recommend obtaining the results that way, rather than using `keepRootFields: true`, if possible.
[@​benjamn](https://togithub.com/benjamn) in [#​8280](https://togithub.com/apollographql/apollo-client/pull/8280) - Internally, Apollo Client now controls the execution of development-only code using the `__DEV__` global variable, rather than `process.env.NODE_ENV`. While this change should not cause any visible differences in behavior, it will increase your minified+gzip bundle size by more than 3.5kB, unless you configure your minifier to replace `__DEV__` with a `true` or `false` constant, the same way you already replace `process.env.NODE_ENV` with a string literal like `"development"` or `"production"`. For an example of configuring a Create React App project without ejecting, see this pull request for our [React Apollo reproduction template](https://togithub.com/apollographql/react-apollo-error-template/pull/51).
[@​benjamn](https://togithub.com/benjamn) in [#​8347](https://togithub.com/apollographql/apollo-client/pull/8347) - Internally, Apollo Client now uses namespace syntax (e.g. `import * as React from "react"`) for imports whose types are re-exported (and thus may appear in `.d.ts` files). This change should remove any need to configure `esModuleInterop` or `allowSyntheticDefaultImports` in `tsconfig.json`, but might require updating bundler configurations that specify named exports of the `react` and `prop-types` packages, to include exports like `createContext` and `createElement` ([example](https://togithub.com/apollographql/apollo-client/commit/16b08e1af9ba9934041298496e167aafb128c15d)).
[@​devrelm](https://togithub.com/devrelm) in [#​7742](https://togithub.com/apollographql/apollo-client/pull/7742) - Respect `no-cache` fetch policy (by not reading any `data` from the cache) for `loading: true` results triggered by `notifyOnNetworkStatusChange: true`.
[@​jcreighton](https://togithub.com/jcreighton) in [#​7761](https://togithub.com/apollographql/apollo-client/pull/7761) - The TypeScript return types of the `getLastResult` and `getLastError` methods of `ObservableQuery` now correctly include the possibility of returning `undefined`. If you happen to be calling either of these methods directly, you may need to adjust how the calling code handles the methods' possibly-`undefined` results.
[@​benjamn](https://togithub.com/benjamn) in [#​8394](https://togithub.com/apollographql/apollo-client/pull/8394) - Log non-fatal `invariant.error` message when fields are missing from result objects written into `InMemoryCache`, rather than throwing an exception. While this change relaxes an exception to be merely an error message, which is usually a backwards-compatible change, the error messages are logged in more cases now than the exception was previously thrown, and those new error messages may be worth investigating to discover potential problems in your application. The errors are not displayed for `@client`-only fields, so adding `@client` is one way to handle/hide the errors for local-only fields. Another general strategy is to use a more precise query to write specific subsets of data into the cache, rather than reusing a larger query that contains fields not present in the written `data`.
[@​benjamn](https://togithub.com/benjamn) in [#​8416](https://togithub.com/apollographql/apollo-client/pull/8416) - The [`nextFetchPolicy`](https://togithub.com/apollographql/apollo-client/pull/6893) option for `client.watchQuery` and `useQuery` will no longer be removed from the `options` object after it has been applied, and instead will continue to be applied any time `options.fetchPolicy` is reset to another value, until/unless the `options.nextFetchPolicy` property is removed from `options`.
[@​benjamn](https://togithub.com/benjamn) in [#​8465](https://togithub.com/apollographql/apollo-client/pull/8465) - The `fetchMore`, `subscribeToMore`, and `updateQuery` functions returned from the `useQuery` hook may now return undefined in edge cases where the functions are called when the component is unmounted
[@​noghartt](https://togithub.com/noghartt) in [#​7980](https://togithub.com/apollographql/apollo-client/pull/7980). ##### Bug fixes - In Apollo Client 2.x, a `refetch` operation would always replace existing data in the cache. With the introduction of field policy `merge` functions in Apollo Client 3, existing field values could be inappropriately combined with incoming field values by a custom `merge` function that does not realize a `refetch` has happened. To give you more control over this behavior, we have introduced an `overwrite?: boolean = false` option for `cache.writeQuery` and `cache.writeFragment`, and an option called `refetchWritePolicy?: "merge" | "overwrite"` for `client.watchQuery`, `useQuery`, and other functions that accept `WatchQueryOptions`. You can use these options to make sure any `merge` functions involved in cache writes for `refetch` operations get invoked with `undefined` as their first argument, which simulates the absence of any existing data, while still giving the `merge` function a chance to determine the internal representation of the incoming data. The default behaviors are `overwrite: true` and `refetchWritePolicy: "overwrite"`, which restores the Apollo Client 2.x behavior, but (if this change causes any problems for your application) you can easily recover the previous merging behavior by setting a default value for `refetchWritePolicy` in `defaultOptions.watchQuery`: ```ts new ApolloClient({ defaultOptions: { watchQuery: { refetchWritePolicy: "merge", }, }, }) ``` [@​benjamn](https://togithub.com/benjamn) in [#​7810](https://togithub.com/apollographql/apollo-client/pull/7810) - Make sure the `MockedResponse` `ResultFunction` type is re-exported.
[@​hwillson](https://togithub.com/hwillson) in [#​8315](https://togithub.com/apollographql/apollo-client/pull/8315) - Fix polling when used with `skip`.
[@​brainkim](https://togithub.com/brainkim) in [#​8346](https://togithub.com/apollographql/apollo-client/pull/8346) - `InMemoryCache` now coalesces `EntityStore` updates to guarantee only one `store.merge(id, fields)` call per `id` per cache write.
[@​benjamn](https://togithub.com/benjamn) in [#​8372](https://togithub.com/apollographql/apollo-client/pull/8372) - Fix polling when used with ``.
[@​brainkim](https://togithub.com/brainkim) in [#​8414](https://togithub.com/apollographql/apollo-client/pull/8414) - Fix the React integration logging `Warning: Can't perform a React state update on an unmounted component`.
[@​wuarmin](https://togithub.com/wuarmin) in [#​7745](https://togithub.com/apollographql/apollo-client/pull/7745) - Make `ObservableQuery#getCurrentResult` always call `queryInfo.getDiff()`.
[@​benjamn](https://togithub.com/benjamn) in [#​8422](https://togithub.com/apollographql/apollo-client/pull/8422) - Make `readField` default to reading from current object only when the `from` option/argument is actually omitted, not when `from` is passed to `readField` with an undefined value. A warning will be printed when this situation occurs.
[@​benjamn](https://togithub.com/benjamn) in [#​8508](https://togithub.com/apollographql/apollo-client/pull/8508) - The `fetchMore`, `subscribeToMore`, and `updateQuery` functions no longer throw `undefined` errors
[@​noghartt](https://togithub.com/noghartt) in [#​7980](https://togithub.com/apollographql/apollo-client/pull/7980). ### [`v3.3.21`](https://togithub.com/apollographql/apollo-client/blob/HEAD/CHANGELOG.md#Apollo-Client-3321) [Compare Source](https://togithub.com/apollographql/apollo-client/compare/v3.3.20...v3.3.21) ##### Bug fixes - Fix race condition in `@apollo/client/link/context` that could leak subscriptions if the subscription is cancelled before `operation.setContext` is called.
[@​sofianhn](https://togithub.com/sofianhn) in [#​8399](https://togithub.com/apollographql/apollo-client/pull/8399) - Prefer `existing.pageInfo.startCursor` and `endCursor` (if defined) in `read` function of `relayStylePagination` policies.
[@​benjamn](https://togithub.com/benjamn) in [#​8438](https://togithub.com/apollographql/apollo-client/pull/8438) ##### Improvements - Normalize user-provided `HttpLink` headers by lower-casing their names.
[@​benjamn](https://togithub.com/benjamn) in [#​8449](https://togithub.com/apollographql/apollo-client/pull/8449)
apollographql/apollo-server ### [`v2.25.3`](https://togithub.com/apollographql/apollo-server/blob/HEAD/CHANGELOG.md#v2253) [Compare Source](https://togithub.com/apollographql/apollo-server/compare/70a431212bd2d07d68c962cb5ded63ecc6a21963...a725306525a99650af46effb72ae9afe780ed88b) - ⚠️ **SECURITY** `apollo-server-core`: Update default version of the GraphQL Playground React app loaded from the CDN to be `@apollographql/graphql-playground-react@1.7.42`. This patches an XSS vulnerability. Note that if you are pinning the Playground React app version in your app with `new ApolloServer({playground: {version: 'some version'}})`, you will need to update the specified version to 1.7.42 or later to avoid this vulnerability. If you disable GraphQL Playground with `new ApolloServer({playground: false})`, this vulnerability does not affect you. See [advisory GHSA-qm7x-rc44-rrqw](https://togithub.com/apollographql/apollo-server/security/advisories/GHSA-qm7x-rc44-rrqw) for more details. ### [`v2.25.2`](https://togithub.com/apollographql/apollo-server/blob/HEAD/CHANGELOG.md#v2252) [Compare Source](https://togithub.com/apollographql/apollo-server/compare/f47c11d3f40f87797c5a615af0bd0225fb18fda8...70a431212bd2d07d68c962cb5ded63ecc6a21963) - `apollo-server-express`: Update dependencies on `@types/express` and `@types/express-serve-static-core`. [PR #​5352](https://togithub.com/apollographql/apollo-server/pull/5352) ### [`v2.25.1`](https://togithub.com/apollographql/apollo-server/blob/HEAD/CHANGELOG.md#v2251) [Compare Source](https://togithub.com/apollographql/apollo-server/compare/42983b06a381aee6333fd11d5af7bd7fa0d549ec...f47c11d3f40f87797c5a615af0bd0225fb18fda8) - `apollo-server-core`, `apollo-server-express`: Upgrade `subscriptions-transport-ws` dependency and remove unneeded runtime dependency on `ws`. This should enable you to install Apollo Server without depending on versions of `ws` vulnerable to [CVE-2021-32640](https://www.npmjs.com/advisories/1748). Note that the superficial integration of the unmaintained `subscriptions-transport-ws` package will be removed in Apollo Server 3; you can also avoid this vulnerability by disabling the built-in subscription support with `new ApolloServer({subscriptions: false})` and using a maintained package such as `graphql-ws` instead. (Instead of taking this upgrade, you can also upgrade `ws` to `5.2.3`, which was just released.) ### [`v2.25.0`](https://togithub.com/apollographql/apollo-server/blob/HEAD/CHANGELOG.md#v2250) [Compare Source](https://togithub.com/apollographql/apollo-server/compare/9e1bf7df8ce856f62e851a9cf268508eb574e32c...42983b06a381aee6333fd11d5af7bd7fa0d549ec) - `apollo-server-core`: You may now specify your Studio graph as a graph ref (`id@variant`) via the `APOLLO_GRAPH_REF` environment variable or `new ApolloServer({apollo: {graphRef}})` instead of specifying graph ID and graph variant separately. The `apollo` object passed to plugin `serverWillStart` and to gateway `load` now contains a `graphRef` field. - `apollo-server-core`: Fix a race condition where schema reporting could lead to a delay at process shutdown. [PR #​5222](https://togithub.com/apollographql/apollo-server/pull/5222) - `apollo-server-core`: Allow the Fetch API implementation to be overridden for the schema reporting and usage reporting plugins via a new `fetcher` option. [PR #​5179](https://togithub.com/apollographql/apollo-server/pull/5179) - `apollo-server-core`: The `server.executeOperation` method (designed for testing) can now take its `query` as a `DocumentNode` (eg, a `gql`-tagged string) in addition to as a string. (This matches the behavior of the `apollo-server-testing` `createTestClient` function which is now deprecated.) We now recommend this method instead of `apollo-server-testing` in our docs. [Issue #​4952](https://togithub.com/apollographql/apollo-server/issues/4952) - `apollo-server-testing`: Replace README with a deprecation notice explaining how to use `server.executeOperation` instead. [Issue #​4952](https://togithub.com/apollographql/apollo-server/issues/4952) ### [`v2.24.1`](https://togithub.com/apollographql/apollo-server/blob/HEAD/CHANGELOG.md#v2241) [Compare Source](https://togithub.com/apollographql/apollo-server/compare/f2349d0e10633ee79bed152f682e53730175d59b...9e1bf7df8ce856f62e851a9cf268508eb574e32c) - `apollo-server-core`: Fix a typo that could lead to TypeScript compilation when combined with a recent version of `@types/node`. (This bug had no runtime effect.) [PR #​5149](https://togithub.com/apollographql/apollo-server/pull/5149) ### [`v2.24.0`](https://togithub.com/apollographql/apollo-server/blob/HEAD/CHANGELOG.md#v2240) [Compare Source](https://togithub.com/apollographql/apollo-server/compare/8a4cc583b692a30670d1893c01851259dbd70ce1...f2349d0e10633ee79bed152f682e53730175d59b) - `apollo-server-core`: Apollo Studio usage reporting uses a more efficient format which sends fewer detailed traces to Apollo's server. This change should not have a major effect on the experience of using Apollo Studio. This also fixes a bug in all prior versions where all operations were reported to Studio as "uncached". [PR #​4142](https://togithub.com/apollographql/apollo-server/pull/4142)
apollographql/graphql-tag ### [`v2.12.6`](https://togithub.com/apollographql/graphql-tag/blob/HEAD/CHANGELOG.md#v2126) [Compare Source](https://togithub.com/apollographql/graphql-tag/compare/cd2f4d0ab46c515a6628a3bef5600534c7d1a7a0...f2de37aa4396834e00bd08db1fa710ad7b365ada) - Update peer dependencies to allow `graphql` ^16.0.0.
[@​brainkim](https://togithub.com/brainkim) in [#​530](https://togithub.com/apollographql/graphql-tag/pull/530) ### [`v2.12.5`](https://togithub.com/apollographql/graphql-tag/blob/HEAD/CHANGELOG.md#v2125) [Compare Source](https://togithub.com/apollographql/graphql-tag/compare/v2.12.4...cd2f4d0ab46c515a6628a3bef5600534c7d1a7a0) - Also publish `src/` directory to npm, enabling source maps.
[@​maclockard](https://togithub.com/maclockard) in [#​403](https://togithub.com/apollographql/graphql-tag/pull/403) ### [`v2.12.4`](https://togithub.com/apollographql/graphql-tag/blob/HEAD/CHANGELOG.md#v2124-2021-04-29) [Compare Source](https://togithub.com/apollographql/graphql-tag/compare/v2.12.3...v2.12.4) - Allow fragments to be imported by name when using the webpack loader.
[@​dobesv](https://togithub.com/dobesv) in [#​257](https://togithub.com/apollographql/graphql-tag/pull/257) ### [`v2.12.3`](https://togithub.com/apollographql/graphql-tag/blob/HEAD/CHANGELOG.md#v2123) [Compare Source](https://togithub.com/apollographql/graphql-tag/compare/v2.12.2...v2.12.3) - Update `tslib` dependency to version 2.1.0.
[@​benjamn](http://github.com/benjamn) in [#​381](https://togithub.com/apollographql/graphql-tag/pull/381) ### [`v2.12.2`](https://togithub.com/apollographql/graphql-tag/blob/HEAD/CHANGELOG.md#v2122) [Compare Source](https://togithub.com/apollographql/graphql-tag/compare/v2.12.1...v2.12.2) - Avoid using `Object.assign` to attach extra properties to `gql`.
[@​benjamn](http://github.com/benjamn) in [#​380](https://togithub.com/apollographql/graphql-tag/pull/380) ### [`v2.12.1`](https://togithub.com/apollographql/graphql-tag/blob/HEAD/CHANGELOG.md#v2121) [Compare Source](https://togithub.com/apollographql/graphql-tag/compare/v2.12.0...v2.12.1) - To accommodate older versions of TypeScript, usage of the `import type ...` syntax (introduced by [#​325](https://togithub.com/apollographql/graphql-tag/pull/325)) has been removed, fixing issue [#​345](https://togithub.com/apollographql/graphql-tag/issues/345).
[@​benjamn](http://github.com/benjamn) in [#​352](https://togithub.com/apollographql/graphql-tag/pull/352) ### [`v2.12.0`](https://togithub.com/apollographql/graphql-tag/blob/HEAD/CHANGELOG.md#v2120) [Compare Source](https://togithub.com/apollographql/graphql-tag/compare/v2.11.0...v2.12.0) - 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](http://github.com/PowerKiKi) and [@​benjamn](http://github.com/benjamn) in [#​325](https://togithub.com/apollographql/graphql-tag/pull/325)

Configuration

📅 Schedule: "before 7am on Tuesday" in timezone Australia/Sydney.

🚦 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.

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

changeset-bot[bot] commented 3 years ago

⚠️ No Changeset found

Latest commit: 7a0096527c859931073f1d005f1ea2e59572f8e3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR