fix(deps): update dependency @apollo/client to v4 by renovate[bot] · Pull Request #11765 · opencollective/opencollective-frontend

renovate · 2025-12-30T08:44:02Z

This PR contains the following updates:

Package	Change	Age	Confidence
@apollo/client (source)	`3.12.10` -> `4.0.11`

Release Notes

apollographql/apollo-client (@apollo/client)

`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 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

Configuration

📅 Schedule: Branch creation - "every weekday after 2:00 am before 6:00 am,every weekend" (UTC), 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.

vercel · 2025-12-30T08:44:03Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
opencollective-frontend	Error		Dec 30, 2025 9:56am
opencollective-styleguide	Building	Preview, Comment	Dec 30, 2025 9:56am

package.json

  "files": [],
  "dependencies": {
-    "@apollo/client": "3.12.10",
+    "@apollo/client": "4.0.11",


package-lock.json

        "graphql": "14 - 16"
      }
    },
+    "node_modules/@types/apollo-upload-client/node_modules/@apollo/client": {
+      "version": "3.14.0",
+      "resolved": "https://registry.npmjs.org/@apollo/client/-/client-3.14.0.tgz",
+      "integrity": "sha512-0YQKKRIxiMlIou+SekQqdCo0ZTHxOcES+K8vKB53cIDpwABNR0P0yRzPgsbgcj3zRJniD93S/ontsnZsCLZrxQ==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {


sentry · 2025-12-30T09:59:12Z

components/CreateEventForm.tsx

  parent: Pick<Account, 'id' | 'slug' | 'legacyId'>;
  loading: boolean;
-  onSuccess: (event: NonNullable<MutationResult<CreateEventMutation>['data']['createEvent']>) => Promise<void>;
+  onSuccess: (event: NonNullable<useMutation.Result<CreateEventMutation>['data']['createEvent']>) => Promise<void>;


Bug: The type useMutation.Result is used, but it was removed in Apollo Client v4. This will cause a TypeScript compilation error, breaking the build.
_{Severity: CRITICAL | Confidence: High}

🔍 Detailed Analysis

The code in components/CreateEventForm.tsx references useMutation.Result, a type that was removed during the migration to Apollo Client v4. The correct type is MutationResult, which should be imported directly. This invalid type reference will cause the TypeScript compilation to fail, preventing the application from being built or deployed. The issue appears to stem from an automated codemod that incorrectly replaced the old type without importing its valid v4 equivalent.

💡 Suggested Fix

Replace the invalid type useMutation.Result<CreateEventMutation> with MutationResult<CreateEventMutation>. Add the corresponding import import type { MutationResult } from "@apollo/client"; at the top of the file.

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not valid. Location: components/CreateEventForm.tsx#L134 Potential issue: The code in `components/CreateEventForm.tsx` references `useMutation.Result`, a type that was removed during the migration to Apollo Client v4. The correct type is `MutationResult`, which should be imported directly. This invalid type reference will cause the TypeScript compilation to fail, preventing the application from being built or deployed. The issue appears to stem from an automated codemod that incorrectly replaced the old type without importing its valid v4 equivalent.

_{Did we get this right? 👍 / 👎 to inform future reviews.}
_{Reference ID: 8022637}

renovate · 2025-12-30T13:03:32Z

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

fix(deps): update dependency @apollo/client to v4

a98919a

vercel bot had a problem deploying to Preview – opencollective-frontend December 30, 2025 08:45 Failure

sentry bot reviewed Dec 30, 2025

View reviewed changes

run codemods

e928977

vercel bot had a problem deploying to Preview – opencollective-frontend December 30, 2025 09:56 Failure

sentry bot reviewed Dec 30, 2025

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(deps): update dependency @apollo/client to v4#11765

fix(deps): update dependency @apollo/client to v4#11765
renovate[bot] wants to merge 2 commits intomainfrom
renovate/major-apollo-graphql-packages

renovate bot commented Dec 30, 2025

Uh oh!

vercel bot commented Dec 30, 2025 •

edited

Loading

Uh oh!

This comment was marked as outdated.

Uh oh!

This comment was marked as outdated.

Uh oh!

sentry bot Dec 30, 2025

Uh oh!

renovate bot commented Dec 30, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

renovate bot commented Dec 30, 2025

Release Notes

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

Patch Changes

Configuration

Uh oh!

vercel bot commented Dec 30, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

This comment was marked as outdated.

Uh oh!

This comment was marked as outdated.

Uh oh!

sentry bot Dec 30, 2025

Choose a reason for hiding this comment

Uh oh!

renovate bot commented Dec 30, 2025

Edited/Blocked Notification

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

vercel bot commented Dec 30, 2025 •

edited

Loading