Update Apollo GraphQL packages #483

renovate · 2024-11-12T05:51:26Z

This PR contains the following updates:

Package	Change	Type	Update
@apollo/client (source)	`^3.11.9` -> `^3.13.1`	dependencies	minor
apollo-server-core (source)	`^3.13.0` -> `^4.0.0`	dependencies	replacement
apollo-server-express (source)	`^3.13.0` -> `^4.0.0`	dependencies	replacement

This is a special PR that replaces apollo-server-core with the community suggested minimal stable replacement version.

This is a special PR that replaces apollo-server-express with the community suggested minimal stable replacement version.

Release Notes

apollographql/apollo-client (@apollo/client)

`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

#12171 e1efe74 Thanks @phryneas! - Fix import extension in masking entry point.

`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 @jerelmiller! - Provide a codemod that applies @unmask to all named fragments for all operations and fragments.

Learn how to use the codemod in the incremental adoption documentation.
#12134 cfaf4ef Thanks @jerelmiller! - Fix issue where data went missing when an unmasked fragment in migrate mode selected fields that the parent did not.
#12154 d933def Thanks @phryneas! - Data masking types: handle overlapping nested array types and fragments on interface types.
#12139 5a53e15 Thanks @phryneas! - Fix issue where masked data would sometimes get returned when the field was part of a child fragment from a fragment unmasked by the parent query.
#12123 8422a30 Thanks @jerelmiller! - Warn when using data masking with "no-cache" operations.
#12139 5a53e15 Thanks @phryneas! - Fix issue where the warning emitted by @unmask(mode: "migrate") would trigger unnecessarily when the fragment was used alongside a masked fragment inside an inline fragment.
#12114 1d4ce00 Thanks @jerelmiller! - Fix error when combining @unmask and @defer directives on a fragment spread when data masking is enabled.
#12130 1e7d009 Thanks @jerelmiller! - Fix error thrown when applying unmask migrate mode warnings on interface types with selection sets that contain inline fragment conditions.
#12152 78137ec Thanks @phryneas! - Add a helper that will skip the TS unmasking alorithm when no fragments are present on type level
#12126 d10d702 Thanks @jerelmiller! - Ensure documents unchanged by the codemod are left untouched.
#12133 a6ece37 Thanks @jerelmiller! - Ensure null is retained in nullable types when unmasking a type with the Unmasked helper type.
#12139 5a53e15 Thanks @phryneas! - Fix issue that threw errors when masking partial data with @unmask(mode: "migrate").

`v3.11.10`

Compare Source

Patch Changes

#12093 1765668 Thanks @mgmolisani! - Fixed a bug when evaluating the devtools flag with the new syntax devtools.enabled that could result to true when explicitly set to false.

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.

👻 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 · 2024-11-12T05:51:26Z

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

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: starter-api@undefined
npm error Found: graphql@15.10.1
npm error node_modules/graphql
npm error   graphql@"^15.10.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer graphql@"^16.6.0" from @apollo/server@4.11.3
npm error node_modules/@apollo/server
npm error   @apollo/server@"^4.0.0" 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 /tmp/renovate/cache/others/npm/_logs/2025-02-14T19_29_28_430Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-02-14T19_29_28_430Z-debug-0.log

sonarqubecloud · 2024-12-13T06:33:46Z

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

auto-assign bot requested review from dkarnutsch, fraxachun, johnnyomair, manuelblum, nsams and thomasdax98 November 12, 2024 05:51

renovate bot force-pushed the renovate/apollo-graphql-packages branch from 2a2da87 to 6d63156 Compare November 12, 2024 14:36

johnnyomair removed their request for review November 13, 2024 07:26

renovate bot force-pushed the renovate/apollo-graphql-packages branch from 6d63156 to 96b9050 Compare November 14, 2024 12:49

github-actions bot requested a review from johnnyomair November 14, 2024 12:49

renovate bot added the dependencies Pull requests that update a dependency file label Nov 15, 2024

renovate bot changed the title ~~fix(deps): update apollo graphql packages~~ Update Apollo GraphQL packages Nov 15, 2024

johnnyomair removed their request for review November 19, 2024 15:26

renovate bot force-pushed the renovate/apollo-graphql-packages branch from 96b9050 to 8818801 Compare November 20, 2024 11:06

renovate bot force-pushed the renovate/apollo-graphql-packages branch 8 times, most recently from c557df6 to 7a07ef3 Compare December 5, 2024 22:24

renovate bot force-pushed the renovate/apollo-graphql-packages branch 2 times, most recently from 7d65ca5 to 82313a2 Compare December 12, 2024 15:53

renovate bot force-pushed the renovate/apollo-graphql-packages branch 2 times, most recently from 7795155 to 3cc69ef Compare December 19, 2024 22:36

renovate bot force-pushed the renovate/apollo-graphql-packages branch 2 times, most recently from 8021f6c to 0b15bd2 Compare January 10, 2025 10:17

renovate bot force-pushed the renovate/apollo-graphql-packages branch 2 times, most recently from 423ecc1 to b92294b Compare January 16, 2025 15:01

renovate bot force-pushed the renovate/apollo-graphql-packages branch 4 times, most recently from 065d971 to ce233f2 Compare January 27, 2025 17:38

renovate bot force-pushed the renovate/apollo-graphql-packages branch 3 times, most recently from bcfb287 to 62df638 Compare February 3, 2025 22:22

thomasdax98 removed their request for review February 5, 2025 07:20

renovate bot force-pushed the renovate/apollo-graphql-packages branch 6 times, most recently from 47f987f to 741d494 Compare February 13, 2025 21:06

Update Apollo GraphQL packages

9b0a6dd

renovate bot force-pushed the renovate/apollo-graphql-packages branch from 741d494 to 9b0a6dd Compare February 14, 2025 19:29

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update Apollo GraphQL packages #483

Update Apollo GraphQL packages #483

renovate bot commented Nov 12, 2024 •

edited

Loading

renovate bot commented Nov 12, 2024 •

edited

Loading

sonarqubecloud bot commented Dec 13, 2024

Update Apollo GraphQL packages #483

Are you sure you want to change the base?

Update Apollo GraphQL packages #483

Conversation

renovate bot commented Nov 12, 2024 • edited Loading

Release Notes

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

Patch Changes

Configuration

renovate bot commented Nov 12, 2024 • edited Loading

⚠️ Artifact update problem

File name: api/package-lock.json

sonarqubecloud bot commented Dec 13, 2024

Quality Gate passed

renovate bot commented Nov 12, 2024 •

edited

Loading

renovate bot commented Nov 12, 2024 •

edited

Loading