fix(deps): update apollo graphql packages (major) by renovate[bot] · Pull Request #1738 · 1-Platform/one-platform

renovate · 2023-09-01T01:26:57Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@apollo/client (source)	`3.2.5` → `4.1.5`
@apollo/client (source)	`3.3.19` → `4.1.5`
@apollo/gateway (source)	`0.42.0` → `2.13.1`
apollo-server-express (source)	`2.25.2` → `3.13.0`
graphql-subscriptions	`^1.2.1` → `^3.0.0`

Release Notes

apollographql/apollo-client (@apollo/client)

`v4.1.5`

Compare Source

Patch Changes

#13155 3ba1583 Thanks @jerelmiller! - Fix an issue where useQuery would poll with pollInterval when skip was initialized to true.
#13135 fd42142 Thanks @jerelmiller! - Fix issue where client.query would apply options from defaultOptions.watchQuery.

`v4.1.4`

Compare Source

Patch Changes

#13124 578081f Thanks @Re-cool! - Ensure PersistedQueryLink merges http and fetchOptions context values instead of overwriting them.

`v4.1.3`

Compare Source

Patch Changes

#13111 bf46fe0 Thanks @RogerHYang! - Fix createFetchMultipartSubscription to support cancellation via AbortController

Previously, calling dispose() or unsubscribe() on a subscription created by createFetchMultipartSubscription had no effect - the underlying fetch request would continue running until completion. This was because no AbortController was created or passed to fetch(), and no cleanup function was returned from the Observable.

`v4.1.2`

Compare Source

Patch Changes

#13105 8b62263 Thanks @phryneas! - ssrMode, ssrForceFetchDelay or prioritizeCacheValues should not override fetchPolicy: 'cache-only', fetchPolicy: 'no-cache', fetchPolicy: 'standby', skip: true, or skipToken when reading the initial value of an ObservableQuery.
#13105 8b62263 Thanks @phryneas! - Fix skipToken in useQuery with prerenderStatic and related SSR functions.
#13105 8b62263 Thanks @phryneas! - Avoid fetches with fetchPolicy: no-cache in useQuery with prerenderStatic and related SSR functions.

`v4.1.1`

Compare Source

Patch Changes

#13103 dee7dcf Thanks @jerelmiller! - Ensure @client fields that are children of aliased server fields are resolved correctly.

`v4.1.0`

Compare Source

Minor Changes

#13043 65e66ca Thanks @jerelmiller! - Support headers transport for enhanced client awareness.
#12927 785e223 Thanks @jerelmiller! - You can now provide a callback function as the context option on the mutate function returned by useMutation. The callback function is called with the value of the context option provided to the useMutation hook. This is useful if you'd like to merge the context object provided to the useMutation hook with a value provided to the mutate function.
```
function MyComponent() {
  const [mutate, result] = useMutation(MUTATION, {
    context: { foo: true },
  });

  async function runMutation() {
    await mutate({
      // sends context as { foo: true, bar: true }
      context: (hookContext) => ({ ...hookContext, bar: true }),
    });
  }

  // ...
}
```
#12923 94ea3e3 Thanks @jerelmiller! - Fix an issue where deferred payloads that returned arrays with fewer items than the original cached array would retain items from the cached array. This change includes @stream arrays where stream arrays replace the cached arrays.
#12927 96b531f Thanks @jerelmiller! - Don't set the fallback value of a @client field to null when a read function is defined. Instead the read function will be called with an existing value of undefined to allow default arguments to be used to set the returned value.

When a read function is not defined nor is there a defined resolver for the field, warn and set the value to null only in that instance.
#12927 45ebb52 Thanks @jerelmiller! - Add support for from: null in client.watchFragment and cache.watchFragment. When from is null, the emitted result is:
```
{
  data: null,
  dataState: "complete",
  complete: true,
}
```
#12926 2b7f2c1 Thanks @jerelmiller! - Support the newer incremental delivery format for the @defer directive implemented in graphql@17.0.0-alpha.9. Import the GraphQL17Alpha9Handler to use the newer incremental delivery format with @defer.
```
import { GraphQL17Alpha9Handler } from "@&#8203;apollo/client/incremental";

const client = new ApolloClient({
  // ...
  incrementalHandler: new GraphQL17Alpha9Handler(),
});
```
[!NOTE]
In order to use the GraphQL17Alpha9Handler, the GraphQL server MUST implement the newer incremental delivery format. You may see errors or unusual behavior if you use the wrong handler. If you are using Apollo Router, continue to use the Defer20220824Handler because Apollo Router does not yet support the newer incremental delivery format.
#12927 45ebb52 Thanks @jerelmiller! - Add support for arrays with useFragment, useSuspenseFragment, and client.watchFragment. This allows the ability to use a fragment to watch multiple entities in the cache. Passing an array to from will return data as an array where each array index corresponds to the index in the from array.
```
function MyComponent() {
  const result = useFragment({
    fragment,
    from: [item1, item2, item3],
  });

  // `data` is an array with 3 items
  console.log(result); // { data: [{...}, {...}, {...}], dataState: "complete", complete: true }
}
```

#12927 45ebb52 Thanks @jerelmiller! - Add a getCurrentResult function to the observable returned by client.watchFragment and cache.watchFragment that returns the current value for the watched fragment.

const observable = client.watchFragment({
  fragment,
  from: { __typename: "Item", id: 1 },
});

console.log(observable.getCurrentResult());
// {
//   data: {...},
//   dataState: "complete",
//   complete: true,
// }

#13038 109efe7 Thanks @jerelmiller! - Add the from option to readFragment, watchFragment, and updateFragment.
#12918 2e224b9 Thanks @jerelmiller! - Add support for the @stream directive on both the Defer20220824Handler and the GraphQL17Alpha2Handler.

[!NOTE]
The implementations of @stream differ in the delivery of incremental results between the different GraphQL spec versions. If you upgrading from the older format to the newer format, expect the timing of some incremental results to change.
#13056 b224efc Thanks @jerelmiller! - InMemoryCache no longer filters out explicitly returned undefined items from read functions for array fields. This now makes it possible to create read functions on array fields that return partial data and trigger a fetch for the full list.
#13058 121a2cb Thanks @jerelmiller! - Add an extensions option to cache.write, cache.writeQuery, and client.writeQuery. This makes extensions available in cache merge functions which can be accessed with the other merge function options.

As a result of this change, any extensions returned in GraphQL operations are now available in merge in the cache writes for these operations.
#12927 96b531f Thanks @jerelmiller! - Add an abstract resolvesClientField function to ApolloCache that can be used by caches to tell LocalState if it can resolve a @client field when a local resolver is not defined.

LocalState will emit a warning and set a fallback value of null when no local resolver is defined and resolvesClientField returns false, or isn't defined. Returning true from resolvesClientField signals that a mechanism in the cache will set the field value. In this case, LocalState won't set the field value.
#13078 bf1e0dc Thanks @phryneas! - Use the default stream merge function for @stream fields only if stream info is present. This change means that using the older Defer20220824Handler will not use the default stream merge function and will instead truncate the streamed array on the first chunk.

Patch Changes

#12884 d329790 Thanks @phryneas! - Ensure that PreloadedQueryRef instances are unsubscribed when garbage collected
#13086 1a1d408 Thanks @phryneas! - Change the returned value from null to {} when all fields in a query were skipped.

This also fixes a bug where useSuspenseQuery would suspend indefinitely when all fields were skipped.
#13010 7627000 Thanks @jerelmiller! - Fix an issue where errors parsed from incremental chunks in ErrorLink might throw when using the GraphQL17Alpha9Handler.
#12927 45ebb52 Thanks @jerelmiller! - Deduplicate watches created by useFragment, client.watchFragment, and cache.watchFragment that contain the same fragment, variables, and identifier. This should improve performance in situations where a useFragment or a client.watchFragment is used to watch the same object in multiple places of an application.
#12927 259ae9b Thanks @jerelmiller! - Allow FragmentType not only to be called as FragmentType<TData>, but also as FragmentType<TypedDocumentNode>.
#12925 5851800 Thanks @jerelmiller! - Fix an issue where calling fetchMore with @defer or @stream would not rerender incremental results as they were streamed.
#12927 9e55188 Thanks @jerelmiller! - Truncate @stream arrays only on last chunk by default.
#13083 f3c2be1 Thanks @phryneas! - Expose the ExtensionsWithStreamInfo type for extensions in Cache.writeQuery, Cache.write and Cache.update so other cache implementations also can correctly access them.
#12923 94ea3e3 Thanks @jerelmiller! - Improve the cache data loss warning message when existing or incoming is an array.
#12927 4631175 Thanks @jerelmiller! - Ignore top-level data values on subsequent chunks in incremental responses.
#12927 2be8de2 Thanks @jerelmiller! - Create mechanism to add experimental features to Apollo Client
#12927 96b531f Thanks @jerelmiller! - Ensure LocalState doesn't try to read from the cache when using a no-cache fetch policy.
#12927 bb8ed7b Thanks @jerelmiller! - Ensure an error is thrown when @stream is detected and an incrementalDelivery handler is not configured.
#13053 23ca0ba Thanks @phryneas! - Use memoized observable mapping when using watchFragment, useFragment or useSuspenseFragment.
#12927 44706a2 Thanks @jerelmiller! - Add helper type QueryRef.ForQuery<TypedDocumentNode>
#13082 c257418 Thanks @phryneas! - Pass streamInfo through result extensions as a WeakRef.
#12927 4631175 Thanks @jerelmiller! - Fix the Defer20220824Handler.SubsequentResult type to match the FormattedSubsequentIncrementalExecutionResult type in graphql@17.0.0-alpha.2.
#12927 96b531f Thanks @jerelmiller! - Warn when using a no-cache fetch policy without a local resolver defined. no-cache queries do not read or write to the cache which meant no-cache queries are silently incomplete when the @client field value was handled by a cache read function.
#12927 5776ea0 Thanks @jerelmiller! - Update the accept header used with the GraphQL17Alpha9Handler to multipart/mixed;incrementalSpec=v0.2 to ensure the newest incremental delivery format is requested.
#12927 45ebb52 Thanks @jerelmiller! - DeepPartial<Array<TData>> now returns Array<DeepPartial<TData>> instead of Array<DeepPartial<TData | undefined>>.
#13071 99ffe9a Thanks @phryneas! - prerenderStatic: Expose return value of renderFunction to userland, fix aborted property.

This enables usage of resumeAndPrerender with React 19.2.
#13026 05eee67 Thanks @jerelmiller! - Reduce the number of observables created by watchFragment by reusing existing observables as much as possible. This should improve performance when watching the same item in the cache multiple times after a cache update occurs.
#13010 7627000 Thanks @jerelmiller! - Handle @stream payloads that send multiple items in the same chunk when using the Defer20220824Handler.
#13010 7627000 Thanks @jerelmiller! - Handle an edge case with the Defer20220824Handler where an error for a @stream item that bubbles to the @stream boundary (such as an item returning null for a non-null array item) would write items from future chunks to the wrong array index. In these cases, the @stream field is no longer processed and future updates to the field are ignored. This prevents runtime errors that TypeScript would otherwise not be able to catch.
#13081 1e06ad7 Thanks @jerelmiller! - Avoid calling merge functions more than once for the same incremental chunk.

`v4.0.13`

Compare Source

Patch Changes

#13094 9cbe2c2 Thanks @phryneas! - Ensure that compact and mergeOptions preserve symbol keys.

This fixes an issue where the change introduced in 4.0.11 via #13049 would not
be applied if defaultOptions for watchQuery were declared.

Please note that compact and mergeOptions are considered internal utilities
and they might have similar behavior changes in future releases.
Do not use them in your application code - a change like this is not considered
breaking and will not be announced as such.

`v4.0.12`

Compare Source

Patch Changes

#12884 d329790 Thanks @phryneas! - Ensure that PreloadedQueryRef instances are unsubscribed when garbage collected
#13069 9cad04a Thanks @jerelmiller! - Truncate @stream arrays only on last chunk by default

`v4.0.11`

Compare Source

Patch Changes

#13050 8020829 Thanks @phryneas! - Replace usage of findLast with more backwards-compatible methods.
#13049 05638de Thanks @phryneas! - Fixes an issue where queries starting with skipToken or lazy queries from useLazyQuery were included in client.refetchQueries() before they had been executed for the first time. While generally queries with a standby fetchPolicy should be included in refetch, these queries never had variables passed in, so they should be excluded until they have run once and received their actual variables.

These queries are now properly excluded from refetch operations until after their initial execution.

This change adds a new hidden option to client.watchQuery, [variablesUnknownSymbol], which may be set true for queries starting with a fetchPolicy of standby. It will only be applied when creating the ObservableQuery instance and cannot be changed later. This flag indicates that the query's variables are not yet known, and thus it should be excluded from refetch operations until they are.
This option is not meant for everyday use and is intended for framework integrations only.

Patch Changes

#12993 8f3bc9b Thanks @jerelmiller! - Fix an issue where switching from options with variables to skipToken with useSuspenseQuery and useBackgroundQuery would create a new ObservableQuery. This could cause unintended refetches where variables were absent in the request when the query was referenced with refetchQueries.

`v4.0.8`

Compare Source

Patch Changes

#12983 f6d0efa Thanks @CarsonF! - Fix cache.modify() mapping readonly arrays to singular reference

`v4.0.7`

Compare Source

Patch Changes

#12950 5b4f36a Thanks @jerelmiller! - Don't send operationType in the payload sent by GraphQLWsLink.

`v4.0.6`

Compare Source

Patch Changes

#12937 3b0d89b Thanks @phryneas! - Fix a problem with fetchMore where the loading state wouldn't reset if the result wouldn't result in a data update.

`v4.0.5`

Compare Source

Patch Changes

#12920 e2fc385 Thanks @phryneas! - Fix an invariance type error in the MockedResponse type.

`v4.0.4`

Compare Source

Patch Changes

#12892 db8a04b Thanks @jerelmiller! - Prevent unhandled rejections from the promise returned by calling the mutate function from the useMutation hook.
#12899 5352c12 Thanks @phryneas! - Fix an issue when invariant is called by external libraries when no dev error message handler is loaded.
#12895 71f2517 Thanks @jerelmiller! - Support skipToken with useQuery to provide a more type-safe way to skip query execution.
```
import { skipToken, useQuery } from "@&#8203;apollo/client/react";

// Use `skipToken` in place of `skip: true` for better type safety
// for required variables
const { data } = useQuery(QUERY, id ? { variables: { id } } : skipToken);
```
Note: this change is provided as a patch within the 4.0 minor version because the changes to TypeScript validation with required variables in version 4.0 made using the skip option more difficult.
#12900 c0d5be7 Thanks @phryneas! - Use named export equal instead of default from "@wry/equality"

`v4.0.3`

Compare Source

Patch Changes

#12887 6f6ca47 Thanks @phryneas! - Fix accidental deep re-export from /react out of /react/internals
#12890 019b422 Thanks @jerelmiller! - Ensure the variables option for useMutation provides proper IntelliSense suggestions.

`v4.0.2`

Compare Source

Patch Changes

#12880 56fac52 Thanks @phryneas! - restore getMemoryInternals access in dev builds

`v4.0.1`

Compare Source

Patch Changes

#12876 b00f231 Thanks @phryneas! - Fix CJS build output for invariantErrorCodes
#12866 0d1614a Thanks @jerelmiller! - Export isNetworkStatusInFlight from @apollo/client/utilities. Add isNetworkStatusSettled to @apollo/client/utilities and re-export it from @apollo/client with a deprecation.

`v4.0.0`

Compare Source

`v3.14.0`

Compare Source

Minor Changes

#12752 8b779b4 Thanks @jerelmiller! - Add deprecations and warnings to remaining APIs changed in Apollo Client 4.0.
#12746 0bcd2f4 Thanks @jerelmiller! - Add warnings and deprecations for options and methods for all React APIs.
#12751 567cad8 Thanks @jerelmiller! - Add @deprecated tags to all properties returned from any query API (e.g. client.query, observableQuery.refetch, etc.), client.mutate, and client.subscribe that are no longer available in Apollo Client 4.0.
#12746 0bcd2f4 Thanks @jerelmiller! - Add preloadQuery.toPromise(queryRef) as a replacement for queryRef.toPromise(). queryRef.toPromise() has been removed in Apollo Client 4.0 in favor of preloadQuery.toPromise and is now considered deprecated.
#12736 ea89440 Thanks @jerelmiller! - Add deprecations and deprecation warnings for ApolloClient options and methods.
#12763 5de6a3d Thanks @jerelmiller! - Version bump only to release latest as rc.
#12459 1c5a031 Thanks @jerelmiller! - Reset addTypenameTransform and fragments caches when calling cache.gc() only when resetResultCache is true.
#12743 92ad409 Thanks @jerelmiller! - Add deprecations and warnings for addTypename in InMemoryCache and MockedProvider.
#12743 92ad409 Thanks @jerelmiller! - Add deprecations and warnings for canonizeResults.
#12751 567cad8 Thanks @jerelmiller! - Warn when using a standby fetch policy with client.query.

Patch Changes

#12750 ecf3de1 Thanks @phryneas! - Prevent field policies from overwriting/merging into supertype field policies.

`v3.13.9`

Compare Source

Patch Changes

#12804 32c9aa9 Thanks @phryneas! - Fix a possible race condition on queries that were reobserved before they were subscribed to the first time.

`v3.13.8`

Compare Source

Patch Changes

#12567 c19d415 Thanks @thearchitector! - Fix in-flight multipart urql subscription cancellation

`v3.13.7`

Compare Source

Patch Changes

#12540 0098932 Thanks @phryneas! - Refactor: Move notification scheduling logic from QueryInfo to ObservableQuery
#12540 0098932 Thanks @phryneas! - Refactored cache emit logic for ObservableQuery. This should be an invisible change.

`v3.13.6`

Compare Source

Patch Changes

#12285 cdc55ff Thanks @phryneas! - keep ObservableQuery created by useQuery non-active before it is first subscribed

`v3.13.5`

Compare Source

Patch Changes

#12461 12c8d06 Thanks @jerelmiller! - Fix an issue where a cache-first query would return the result for previous variables when a cache update is issued after simultaneously changing variables and skipping the query.

`v3.13.4`

Compare Source

Patch Changes

#12420 fee9368 Thanks @jorenbroekema! - Use import star from rehackt to prevent issues with importing named exports from external CJS modules.

`v3.13.3`

Compare Source

Patch Changes

#12362 f6d387c Thanks @jerelmiller! - Fixes an issue where calling observableQuery.getCurrentResult() when the errorPolicy was set to all would return the networkStatus as NetworkStatus.ready when there were errors returned in the result. This has been corrected to report NetworkStatus.error.

This bug also affected the useQuery and useLazyQuery hooks and may affect you if you check for networkStatus in your component.

`v3.13.2`

Compare Source

Patch Changes

#12409 6aa2f3e Thanks @phryneas! - To mitigate problems when Apollo Client ends up more than once in the bundle, some unique symbols were converted into Symbol.for calls.
#12392 644bb26 Thanks @Joja81! - Fixes an issue where the DeepOmit type would turn optional properties into required properties. This should only affect you if you were using the omitDeep or stripTypename utilities exported by Apollo Client.
#12404 4332b88 Thanks @jerelmiller! - Show NaN rather than converting to null in debug messages from MockLink for unmatched variables values.

`v3.13.1`

Compare Source

Patch Changes

#12369 bdfc5b2 Thanks @phryneas! - ObervableQuery.refetch: don't refetch with cache-and-network, swich to network-only instead
#12375 d3f8f13 Thanks @jerelmiller! - Export the UseSuspenseFragmentOptions type.

`v3.13.0`

Compare Source

Minor Changes

#12066 c01da5d Thanks @jerelmiller! - Adds a new useSuspenseFragment hook.

useSuspenseFragment suspends until data is complete. It is a drop-in replacement for useFragment when you prefer to use Suspense to control the loading state of a fragment. See the documentation for more details.
#12174 ba5cc33 Thanks @jerelmiller! - Ensure errors thrown in the onCompleted callback from useMutation don't call onError.
#12340 716d02e Thanks @phryneas! - Deprecate the onCompleted and onError callbacks of useQuery and useLazyQuery.
For more context, please see the related issue on GitHub.
#12276 670f112 Thanks @Cellule! - Provide a more type-safe option for the previous data value passed to observableQuery.updateQuery. Using it could result in crashes at runtime as this callback could be called with partial data even though its type reported the value as a complete result.

The updateQuery callback function is now called with a new type-safe previousData property and a new complete property in the 2nd argument that determines whether previousData is a complete or partial result.

As a result of this change, it is recommended to use the previousData property passed to the 2nd argument of the callback rather than using the previous data value from the first argument since that value is not type-safe. The first argument is now deprecated and will be removed in a future version of Apollo Client.
```
observableQuery.updateQuery(
  (unsafePreviousData, { previousData, complete }) => {
    previousData;
    // ^? TData | DeepPartial<TData> | undefined

    if (complete) {
      previousData;
      // ^? TData
    } else {
      previousData;
      // ^? DeepPartial<TData> | undefined
    }
  }
);
```
#12174 ba5cc33 Thanks @jerelmiller! - Reject the mutation promise if errors are thrown in the onCompleted callback of useMutation.

Patch Changes

#12276 670f112 Thanks @Cellule! - Fix the return type of the updateQuery function to allow for undefined. updateQuery had the ability to bail out of the update by returning a falsey value, but the return type enforced a query value.

observableQuery.updateQuery(
  (unsafePreviousData, { previousData, complete }) => {
    if (!complete) {
      // Bail out of the update by returning early
      return;
    }

    // ...
  }
);

#12296 2422df2 Thanks @Cellule! - Deprecate option ignoreResults in useMutation.
Once this option is removed, existing code still using it might see increase in re-renders.
If you don't want to synchronize your component state with the mutation, please use useApolloClient to get your ApolloClient instance and call client.mutate directly.
#12338 67c16c9 Thanks @phryneas! - In case of a multipart response (e.g. with @defer), query deduplication will
now keep going until the final chunk has been received.
#12276 670f112 Thanks @Cellule! - Fix the type of the variables property passed as the 2nd argument to the subscribeToMore callb

Configuration

📅 Schedule: Branch creation - "on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

renovate · 2023-09-01T01:26:59Z

⚠ 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: packages/api-gateway-service/package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: api-gateway@0.2.1
npm ERR! Found: graphql@15.6.0
npm ERR! node_modules/graphql
npm ERR!   graphql@"15.6.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer graphql@"^16.5.0" from @apollo/gateway@2.7.5
npm ERR! node_modules/@apollo/gateway
npm ERR!   dev @apollo/gateway@"2.7.5" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-05-03T11_40_21_307Z-debug-0.log

renovate · 2024-05-26T06:09:09Z

⚠️ Artifact update problem

Renovate failed to update artifacts 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: packages/api-gateway-service/package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: api-gateway@0.2.1
npm ERR! Found: graphql@15.6.0
npm ERR! node_modules/graphql
npm ERR!   graphql@"15.6.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer graphql@"^16.5.0" from @apollo/gateway@2.13.1
npm ERR! node_modules/@apollo/gateway
npm ERR!   dev @apollo/gateway@"2.13.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-02-22T13_16_50_166Z-debug-0.log

File name: packages/api-catalog-service/package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: graphql-redis-subscriptions@2.4.0
npm ERR! Found: graphql-subscriptions@3.0.0
npm ERR! node_modules/graphql-subscriptions
npm ERR!   graphql-subscriptions@"^3.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer graphql-subscriptions@"^1.0.0" from graphql-redis-subscriptions@2.4.0
npm ERR! node_modules/graphql-redis-subscriptions
npm ERR!   graphql-redis-subscriptions@"2.4.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: graphql-subscriptions@1.2.1
npm ERR! node_modules/graphql-subscriptions
npm ERR!   peer graphql-subscriptions@"^1.0.0" from graphql-redis-subscriptions@2.4.0
npm ERR!   node_modules/graphql-redis-subscriptions
npm ERR!     graphql-redis-subscriptions@"2.4.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-02-22T13_16_56_597Z-debug-0.log

renovate bot force-pushed the renovate/major-apollo-graphql-packages branch 3 times, most recently from 01b0a5a to 2b7d323 Compare September 10, 2023 15:07

renovate bot force-pushed the renovate/major-apollo-graphql-packages branch from 2b7d323 to 3c7833d Compare October 1, 2023 08:18

renovate bot force-pushed the renovate/major-apollo-graphql-packages branch from 3c7833d to 20a8e50 Compare October 13, 2023 22:26

renovate bot force-pushed the renovate/major-apollo-graphql-packages branch 2 times, most recently from 9a325a3 to 5d083db Compare November 17, 2023 02:26

renovate bot force-pushed the renovate/major-apollo-graphql-packages branch 2 times, most recently from 6f484f1 to 81794c3 Compare November 28, 2023 01:22

renovate bot force-pushed the renovate/major-apollo-graphql-packages branch 4 times, most recently from 73f1130 to a989add Compare December 12, 2023 10:27

renovate bot force-pushed the renovate/major-apollo-graphql-packages branch from a989add to 5feb13c Compare January 11, 2024 16:12

renovate bot force-pushed the renovate/major-apollo-graphql-packages branch from 5feb13c to 6e582ca Compare January 20, 2024 05:04

renovate bot force-pushed the renovate/major-apollo-graphql-packages branch from 6e582ca to d018064 Compare January 31, 2024 12:08

renovate bot force-pushed the renovate/major-apollo-graphql-packages branch from d018064 to 9523012 Compare March 29, 2024 21:12

renovate bot force-pushed the renovate/major-apollo-graphql-packages branch 2 times, most recently from 8da2c07 to bf75b40 Compare April 22, 2024 11:26

renovate bot force-pushed the renovate/major-apollo-graphql-packages branch from bf75b40 to d603bf6 Compare May 3, 2024 11:40

renovate bot force-pushed the renovate/major-apollo-graphql-packages branch from d603bf6 to f579782 Compare May 26, 2024 06:09

renovate bot force-pushed the renovate/major-apollo-graphql-packages branch from f579782 to 21e6664 Compare June 3, 2024 23:49

renovate bot force-pushed the renovate/major-apollo-graphql-packages branch from 21e6664 to 10ed682 Compare June 23, 2024 15:26

renovate bot force-pushed the renovate/major-apollo-graphql-packages branch from 10ed682 to 9c22e7c Compare July 26, 2024 18:05

renovate bot force-pushed the renovate/major-apollo-graphql-packages branch 2 times, most recently from 86bd4b8 to 1f0def2 Compare October 4, 2024 08:05

renovate bot force-pushed the renovate/major-apollo-graphql-packages branch from 1f0def2 to 2528f27 Compare October 7, 2024 13:32

renovate bot force-pushed the renovate/major-apollo-graphql-packages branch from 2528f27 to 8a559e4 Compare October 20, 2024 08:39

renovate bot force-pushed the renovate/major-apollo-graphql-packages branch from 8a559e4 to 3451014 Compare November 12, 2024 00:49

renovate bot force-pushed the renovate/major-apollo-graphql-packages branch from 3451014 to 2b94e27 Compare December 15, 2024 04:40

renovate bot changed the title ~~chore(deps): update apollo graphql packages (major)~~ fix(deps): update apollo graphql packages (major) Dec 15, 2024

renovate bot force-pushed the renovate/major-apollo-graphql-packages branch from 2b94e27 to 67eb6a1 Compare January 25, 2025 11:32

renovate bot force-pushed the renovate/major-apollo-graphql-packages branch from 67eb6a1 to 71b95c2 Compare February 16, 2025 14:12

renovate bot force-pushed the renovate/major-apollo-graphql-packages branch from 71b95c2 to 1476b07 Compare May 19, 2025 00:24

renovate bot force-pushed the renovate/major-apollo-graphql-packages branch from 1476b07 to c542a47 Compare August 10, 2025 07:52

renovate bot force-pushed the renovate/major-apollo-graphql-packages branch from c542a47 to f54042d Compare September 21, 2025 11:12

renovate bot force-pushed the renovate/major-apollo-graphql-packages branch from f54042d to b339e70 Compare November 23, 2025 12:04

fix(deps): update apollo graphql packages

11dfeeb

renovate bot force-pushed the renovate/major-apollo-graphql-packages branch from b339e70 to 11dfeeb Compare February 22, 2026 13:17

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(deps): update apollo graphql packages (major)#1738

fix(deps): update apollo graphql packages (major)#1738
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/major-apollo-graphql-packages

renovate bot commented Sep 1, 2023 •

edited

Loading

Uh oh!

renovate bot commented Sep 1, 2023 •

edited

Loading

Uh oh!

renovate bot commented May 26, 2024 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate bot commented Sep 1, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Configuration

Uh oh!

renovate bot commented Sep 1, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠ Artifact update problem

File name: packages/api-gateway-service/package-lock.json

Uh oh!

renovate bot commented May 26, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ Artifact update problem

File name: packages/api-gateway-service/package-lock.json

File name: packages/api-catalog-service/package-lock.json

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate bot commented Sep 1, 2023 •

edited

Loading

renovate bot commented Sep 1, 2023 •

edited

Loading

renovate bot commented May 26, 2024 •

edited

Loading