Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Aug 21, 2025

This PR contains the following updates:

Package Change Age Confidence
@apollo/client (source) ^3.13.8 -> ^4.0.0 age confidence

Release Notes

apollographql/apollo-client (@​apollo/client)

v4.0.9

Compare Source

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

v4.0.7

Compare Source

Patch Changes

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

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 "@​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

v4.0.2

Compare Source

Patch Changes

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
Patch Changes

Configuration

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

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

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

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented Aug 21, 2025

⚠️ 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: kompassi-v2-frontend/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @apollo/[email protected]
npm error Found: @apollo/[email protected]
npm error node_modules/@apollo/client
npm error   @apollo/client@"^4.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @apollo/client@"^3.13.0" from @apollo/[email protected]
npm error node_modules/@apollo/client-integration-nextjs
npm error   @apollo/client-integration-nextjs@"^0.12.2" from the root project
npm error
npm error Conflicting peer dependency: @apollo/[email protected]
npm error node_modules/@apollo/client
npm error   peer @apollo/client@"^3.13.0" from @apollo/[email protected]
npm error   node_modules/@apollo/client-integration-nextjs
npm error     @apollo/client-integration-nextjs@"^0.12.2" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-11-11T01_56_37_187Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-11-11T01_56_37_187Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-apollo-graphql-packages branch 4 times, most recently from d25b267 to 094d2bb Compare August 31, 2025 14:42
@renovate renovate bot force-pushed the renovate/major-apollo-graphql-packages branch from 094d2bb to aaf1354 Compare September 2, 2025 20:55
@renovate renovate bot force-pushed the renovate/major-apollo-graphql-packages branch from aaf1354 to 29fd64c Compare September 13, 2025 03:51
@renovate renovate bot force-pushed the renovate/major-apollo-graphql-packages branch 3 times, most recently from bd9adc1 to f8b5ea3 Compare September 30, 2025 19:41
@renovate renovate bot force-pushed the renovate/major-apollo-graphql-packages branch 2 times, most recently from 660867a to 3a18bde Compare October 27, 2025 19:50
@renovate renovate bot force-pushed the renovate/major-apollo-graphql-packages branch from 3a18bde to 0b21c98 Compare October 31, 2025 17:40
@renovate renovate bot force-pushed the renovate/major-apollo-graphql-packages branch from 0b21c98 to 5fb55d0 Compare November 11, 2025 01:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant