fix(deps): update all minor, or patch dependencies on npm by renovate[bot] · Pull Request #587 · cloudnativedaysjp/dreamkast-ui

renovate · 2026-04-26T18:00:33Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@apollo/client (source)	`3.7.17` → `3.14.1`
@auth0/auth0-react	`2.2.0` → `2.18.0`
@graphql-codegen/client-preset (source)	`4.0.1` → `4.8.3`
@paulmillr/qr	`^0.2.1` → `^0.3.0`
@reduxjs/toolkit (source)	`1.9.5` → `1.9.7`
@rtk-query/codegen-openapi (source)	`1.0.0` → `1.2.0`
@sentry/nextjs (source)	`7.60.0` → `7.120.4`
@testing-library/react	`14.0.0` → `14.3.1`
@testing-library/user-event	`14.4.3` → `14.6.1`
@types/actioncable (source)	`5.2.7` → `5.2.11`
@types/axios	`0.14.0` → `0.14.4`
@types/jest (source)	`29.5.3` → `29.5.14`
@types/linkifyjs (source)	`2.1.4` → `2.1.7`
@types/node (source)	`22.17.1` → `22.19.21`
@types/react (source)	`18.2.15` → `18.3.31`
@types/react-dom (source)	`18.2.7` → `18.3.7`
@types/react-gtm-module (source)	`2.0.1` → `2.0.4`
@types/react-slick (source)	`0.23.10` → `0.23.13`
@types/react-test-renderer (source)	`18.0.0` → `18.3.1`
@types/styled-components (source)	`5.1.26` → `5.1.36`
@types/video.js (source)	`7.3.52` → `7.3.58`
axios (source)	`1.4.0` → `1.18.0`
babel-plugin-styled-components (source)	`2.1.4` → `2.3.0`
babel-preset-react-app (source, changelog)	`10.0.1` → `10.1.0`
cross-fetch	`3.1.8` → `3.2.0`
dayjs (source)	`1.11.9` → `1.11.21`
eslint (source)	`8.45.0` → `8.57.1`
eslint-config-next (source)	`14.2.25` → `14.2.35`
eslint-config-prettier	`8.8.0` → `8.10.2`
eslint-plugin-prettier	`4.2.1` → `4.2.5`
eslint-plugin-react	`7.33.0` → `7.37.5`
eslint-plugin-react-hooks (source)	`4.6.0` → `4.6.2`
graphql	`16.7.1` → `16.14.2`
jest (source)	`29.6.1` → `29.7.0`
jest-environment-jsdom (source)	`29.6.1` → `29.7.0`
linkify-react (source)	`4.1.1` → `4.3.3`
linkifyjs (source)	`4.1.1` → `4.3.3`
msw (source)	`1.2.3` → `1.3.5`
notistack (source)	`3.0.1` → `3.0.2`
react (source)	`18.2.0` → `18.3.1`
react-dom (source)	`18.2.0` → `18.3.1`
react-hook-form (source)	`7.45.2` → `7.79.0`
react-redux	`8.1.1` → `8.1.3`
react-router-dom (source)	`6.14.2` → `6.30.4`
react-slick (source)	`^0.29.0` → `^0.31.0`
react-test-renderer (source)	`18.2.0` → `18.3.1`
ts-jest (source)	`29.1.1` → `29.4.11`
ts-node (source)	`10.9.1` → `10.9.2`
typescript (source)	`5.1.6` → `5.9.3`
yarn (source)	`4.14.1` → `4.17.0`

Release Notes

apollographql/apollo-client (@apollo/client)

`v3.14.1`

Compare Source

Patch Changes

#13168 6b84ec0 Thanks @jerelmiller! - Fix issue where muting a deprecation from one entrypoint would not mute the warning when checked in a different entrypoint. This caused some rogue deprecation warnings to appear in the console even though the warnings should have been muted.
#12970 f91fab5 Thanks @acemir! - Add a deprecation message for the variableMatcher option in MockLink.
#13168 6b84ec0 Thanks @jerelmiller! - Ensure deprecation warnings are properly silenced in React hooks when globally disabled.

`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 callback. This was previously reported as the variables type for the subscription itself, but is now properly typed as the query variables.

`v3.12.11`

Compare Source

Patch Changes

#12351 3da908b Thanks @jerelmiller! - Fixes an issue where the wrong networkStatus and loading value was emitted from observableQuery when calling fetchMore with a no-cache fetch policy. The networkStatus now properly reports as ready and loading as false after the result is returned.
#12354 a24ef94 Thanks @phryneas! - Fix missing main.d.cts file

`v3.12.10`

Compare Source

Patch Changes

#12341 f2bb0b9 Thanks @phryneas! - useReadQuery/useQueryRefHandlers: Fix a "hook order" warning that might be emitted in React 19 dev mode.
#12342 219b26b Thanks @phryneas! - Add graphql-ws ^6.0.3 as a valid peerDependency

`v3.12.9`

Compare Source

Patch Changes

#12321 daa4f33 Thanks @jerelmiller! - Fix type of extensions in protocolErrors for ApolloError and the onError link. According to the multipart HTTP subscription protocol, fatal tranport errors follow the GraphQL error format which require extensions to be a map as its value instead of an array.

#12318 b17968b Thanks @jerelmiller! - Allow RetryLink to retry an operation when fatal transport-level errors are emitted from multipart subscriptions.

const retryLink = new RetryLink({
  attempts: (count, operation, error) => {
    if (error instanceof ApolloError) {
      // errors available on the `protocolErrors` field in `ApolloError`
      console.log(error.protocolErrors);
    }

    return true;
  },
});

`v3.12.8`

Compare Source

Patch Changes

#12292 3abd944 Thanks @phryneas! - Remove unused dependency response-iterator
#12287 bf313a3 Thanks @phryneas! - Fixes an issue where client.watchFragment/useFragment with @includes crashes when a separate cache update writes to the conditionally included fields.

`v3.12.7`

Compare Source

Patch Changes

#12281 d638ec3 Thanks @jerelmiller! - Make fatal tranport-level errors from multipart subscriptions available to the error link with the protocolErrors property.
```
const errorLink = onError(({ protocolErrors }) => {
  if (protocolErrors) {
    console.log(protocolErrors);
  }
});
```
#12281 d638ec3 Thanks @jerelmiller! - Fix the array type for the errors field on the ApolloPayloadResult type. This type was always in the shape of the GraphQL error format, per the multipart subscriptions protocol and never a plain string or a JavaScript error object.

`v3.12.6`

Compare Source

Patch Changes

#12267 d57429d Thanks @jerelmiller! - Maintain the TData type when used with Unmasked when TData is not a masked type generated from GraphQL Codegen.
#12270 3601246 Thanks @jerelmiller! - Fix handling of tagged/branded primitive types when used as scalar values with Unmasked.

`v3.12.5`

Compare Source

Patch Changes

#12252 cb9cd4e Thanks @jerelmiller! - Changes the default behavior of the MaybeMasked type to preserve types unless otherwise specified. This change makes it easier to upgrade from older versions of the client where types could have unexpectedly changed in the application due to the default of trying to unwrap types into unmasked types. This change also fixes the compilation performance regression experienced when simply upgrading the client since types are now preserved by default.

A new mode option has now been introduced to allow for the old behavior. See the next section on migrating if you wish to maintain the old default behavior after upgrading to this version.

Migrating from <= v3.12.4

If you've adopted data masking and have opted in to using masked types by setting the enabled property to true, you can remove this configuration entirely:

-declare module "@&#8203;apollo/client" {
-  interface DataMasking {
-    mode: "unmask"
-  }
-}

If you prefer to specify the behavior explicitly, change the property from enabled: true, to mode: "preserveTypes":

declare module "@&#8203;apollo/client" {
  interface DataMasking {
-    enabled: true
+    mode: "preserveTypes"
  }
}

If you rely on the default behavior in 3.12.4 or below and would like to continue to use unmasked types by default, set the mode to unmask:

declare module "@&#8203;apollo/client" {
  interface DataMasking {
    mode: "unmask";
  }
}

`v3.12.4`

Compare Source

Patch Changes

#12236 4334d30 Thanks @charpeni! - Fix an issue with refetchQueries where comparing DocumentNodes internally by references could lead to an unknown query, even though the DocumentNode was indeed an active query—with a different reference.

`v3.12.3`

Compare Source

Patch Changes

#12214 8bfee88 Thanks @phryneas! - Data masking: prevent infinite recursion of ContainsFragmentsRefs type
#12204 851deb0 Thanks @jerelmiller! - Fix Unmasked unwrapping tuple types into an array of their subtypes.
#12204 851deb0 Thanks @jerelmiller! - Ensure MaybeMasked does not try and unwrap types that contain index signatures.
#12204 851deb0 Thanks @jerelmiller! - Ensure MaybeMasked does not try to unwrap the type as Unmasked if the type contains any.

`v3.12.2`

Compare Source

Patch Changes

#12175 84af347 Thanks @jerelmiller! - Update peer deps to allow for React 19 stable release.

`v3.12.1`

Compare Source

Patch Changes

#12351 3da908b Thanks @jerelmiller! - Fixes an issue where the wrong networkStatus and loading value was emitted from observableQuery when calling fetchMore with a no-cache fetch policy. The networkStatus now properly reports as ready and loading as false after the result is returned.
#12354 a24ef94 Thanks @phryneas! - Fix missing main.d.cts file

`v3.12.0`

Compare Source

Minor Changes

Data masking 🎭

#12042 1c0ecbf Thanks @jerelmiller! - Introduces data masking in Apollo Client.

Data masking enforces that only the fields requested by the query or fragment is available to that component. Data masking is best paired with colocated fragments.

To enable data masking in Apollo Client, set the dataMasking option to true.
```
new ApolloClient({
  dataMasking: true,
  // ... other options
});
```
For detailed information on data masking, including how to incrementally adopt it in an existing applications, see the data masking documentation.
#12131 21c3f08 Thanks @jerelmiller! - Allow null as a valid from value in useFragment.

More Patch Changes

#12126 d10d702 Thanks @jerelmiller! - Maintain the existing document if its unchanged by the codemod and move to more naive whitespace formatting
#12150 9ed1e1e Thanks @jerelmiller! - Fix issue when using Unmasked with older versions of TypeScript when used with array fields.
#12116 8ae6e4e Thanks @jerelmiller! - Prevent field accessor warnings when using @unmask(mode: "migrate") on objects that are passed into cache.identify.
#12120 6a98e76 Thanks [@jere

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

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 was generated by Mend Renovate. View the repository job log.

renovate Bot added the dependencies label Apr 26, 2026

renovate Bot requested a review from a team April 26, 2026 18:00

renovate Bot added the dependencies label Apr 26, 2026

renovate Bot force-pushed the renovate/all-minor-or-patch-dependencies-on-npm branch 4 times, most recently from 31fd3b4 to 7ffdcb2 Compare May 3, 2026 00:42

renovate Bot force-pushed the renovate/all-minor-or-patch-dependencies-on-npm branch 5 times, most recently from 9843908 to 5923c47 Compare May 15, 2026 01:13

renovate Bot force-pushed the renovate/all-minor-or-patch-dependencies-on-npm branch 5 times, most recently from 92fb6d2 to 5468dce Compare May 23, 2026 00:58

renovate Bot force-pushed the renovate/all-minor-or-patch-dependencies-on-npm branch 7 times, most recently from 504bb07 to 76210ae Compare June 2, 2026 05:49

renovate Bot force-pushed the renovate/all-minor-or-patch-dependencies-on-npm branch 6 times, most recently from 28defe1 to 52f4ac3 Compare June 10, 2026 10:37

renovate Bot force-pushed the renovate/all-minor-or-patch-dependencies-on-npm branch 7 times, most recently from 0d5d3e2 to fff9cb7 Compare June 17, 2026 22:50

renovate Bot force-pushed the renovate/all-minor-or-patch-dependencies-on-npm branch 2 times, most recently from a74155a to 1e7e3fb Compare June 21, 2026 20:33

fix(deps): update all minor, or patch dependencies on npm

039db84

renovate Bot force-pushed the renovate/all-minor-or-patch-dependencies-on-npm branch from 1e7e3fb to 039db84 Compare June 22, 2026 14:15

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(deps): update all minor, or patch dependencies on npm#587

fix(deps): update all minor, or patch dependencies on npm#587
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-minor-or-patch-dependencies-on-npm

renovate Bot commented Apr 26, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Uh oh!

Conversation

renovate Bot commented Apr 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

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

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Migrating from <= v3.12.4

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Data masking 🎭

More Patch Changes

Configuration

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate Bot commented Apr 26, 2026 •

edited

Loading