Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): pin dependency @apollo/client to v3.11.10 #519

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 2, 2024

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
@apollo/client (source) peerDependencies pin ^3.7.17 -> 3.11.10 age adoption passing confidence
@apollo/client (source) devDependencies minor 3.9.9 -> 3.11.10 age adoption passing confidence

Add the preset :preserveSemverRanges to your config if you don't want to pin your dependencies.


Release Notes

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

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.

v3.11.9

Compare Source

Patch Changes
  • #​12110 a3f95c6 Thanks @​jerelmiller! - Fix an issue where errors returned from a fetchMore call from a Suspense hook would cause a Suspense boundary to be shown indefinitely.

v3.11.8

Compare Source

Patch Changes

v3.11.7

Compare Source

Patch Changes
  • #​12052 e471cef Thanks @​jerelmiller! - Fixes a regression from where passing an invalid identifier to from in useFragment would result in the warning TypeError: Cannot read properties of undefined (reading '__typename').

v3.11.6

Compare Source

Patch Changes

v3.11.5

Compare Source

Patch Changes

v3.11.4

Compare Source

Patch Changes
  • #​11994 41b17e5 Thanks @​jerelmiller! - Update the Modifier function type to allow cache.modify to return deeply partial data.

  • #​11989 e609156 Thanks @​phryneas! - Fix a potential crash when calling clearStore while a query was running.

    Previously, calling client.clearStore() while a query was running had one of these results:

    • useQuery would stay in a loading: true state.
    • useLazyQuery would stay in a loading: true state, but also crash with a "Cannot read property 'data' of undefined" error.

    Now, in both cases, the hook will enter an error state with a networkError, and the promise returned by the useLazyQuery execute function will return a result in an error state.

  • #​11994 41b17e5 Thanks @​jerelmiller! - Prevent accidental distribution on cache.modify field modifiers when a field is a union type array.

v3.11.3

Compare Source

Patch Changes
Potentially disruptive change

When calling fetchMore with a query that has a no-cache fetch policy, fetchMore will now throw if an updateQuery function is not provided. This provides a mechanism to merge the results from the fetchMore call with the query's previous result.

v3.11.2

Compare Source

Patch Changes

v3.11.1

Compare Source

Patch Changes
  • #​11969 061cab6 Thanks @​jerelmiller! - Remove check for window.__APOLLO_CLIENT__ when determining whether to connect to Apollo Client Devtools when connectToDevtools or devtools.enabled is not specified. This now simply checks to see if the application is in development mode.

  • #​11971 ecf77f6 Thanks @​jerelmiller! - Prevent the setTimeout for suggesting devtools from running in non-browser environments.

v3.11.0

Compare Source

Potentially Breaking Fixes
  • #​11789 5793301 Thanks @​phryneas! - Changes usages of the GraphQLError type to GraphQLFormattedError.

    This was a type bug - these errors were never GraphQLError instances
    to begin with, and the GraphQLError class has additional properties that can
    never be correctly rehydrated from a GraphQL result.
    The correct type to use here is GraphQLFormattedError.

    Similarly, please ensure to use the type FormattedExecutionResult
    instead of ExecutionResult - the non-"Formatted" versions of these types
    are for use on the server only, but don't get transported over the network.

  • #​11626 228429a Thanks @​phryneas! - Call nextFetchPolicy with "variables-changed" even if there is a fetchPolicy specified.

    Previously this would only be called when the current fetchPolicy was equal to the fetchPolicy option or the option was not specified. If you use nextFetchPolicy as a function, expect to see this function called more often.

    Due to this bug, this also meant that the fetchPolicy might be reset to the initial fetchPolicy, even when you specified a nextFetchPolicy function. If you previously relied on this behavior, you will need to update your nextFetchPolicy callback function to implement this resetting behavior.

    As an example, if your code looked like the following:

    useQuery(QUERY, {
      nextFetchPolicy(currentFetchPolicy, info) {
        // your logic here
      }
    );

    Update your function to the following to reimplement the resetting behavior:

    useQuery(QUERY, {
      nextFetchPolicy(currentFetchPolicy, info) {
        if (info.reason === 'variables-changed') {
          return info.initialFetchPolicy;
        }
        // your logic here
      }
    );
Minor Changes
Patch Changes

v3.10.8

Compare Source

Patch Changes

v3.10.7

Compare Source

Patch Changes

v3.10.6

Compare Source

Patch Changes

v3.10.5

Compare Source

Patch Changes

v3.10.4

Compare Source

Patch Changes
  • #​11838 8475346 Thanks @​alex-kinokon! - Don’t prompt for DevTools installation for browser extension page

  • #​11839 6481fe1 Thanks @​jerelmiller! - Fix a regression in 3.9.5 where a merge function that returned an incomplete result would not allow the client to refetch in order to fulfill the query.

  • #​11844 86984f2 Thanks @​jerelmiller! - Honor the @nonreactive directive when using cache.watchFragment or the useFragment hook to avoid rerendering when using these directives.

  • #​11824 47ad806 Thanks @​phryneas! - Create branded QueryRef type without exposed properties.

    This change deprecates QueryReference in favor of a QueryRef type that doesn't expose any properties.
    This change also updates preloadQuery to return a new PreloadedQueryRef type, which exposes the toPromise function as it does today. This means that query refs produced by useBackgroundQuery and useLoadableQuery now return QueryRef types that do not have access to a toPromise function, which was never meant to be used in combination with these hooks.

    While we tend to avoid any types of breaking changes in patch releases as this, this change was necessary to support an upcoming version of the React Server Component integration, which needed to omit the toPromise function that would otherwise have broken at runtime.
    Note that this is a TypeScript-only change. At runtime, toPromise is still present on all queryRefs currently created by this package - but we strongly want to discourage you from accessing it in all cases except for the PreloadedQueryRef use case.

    Migration is as simple as replacing all references to QueryReference with QueryRef, so it should be possible to do this with a search & replace in most code bases:

    -import { QueryReference } from '@​apollo/client'
    +import { QueryRef } from '@​apollo/client'
    
    - function Component({ queryRef }: { queryRef: QueryReference<TData> }) {
    + function Component({ queryRef }: { queryRef: QueryRef<TData> }) {
      // ...
    }
  • #​11845 4c5c820 Thanks @​jerelmiller! - Remove @nonreactive directives from queries passed to MockLink to ensure they are properly matched.

  • #​11837 dff15b1 Thanks @​jerelmiller! - Fix an issue where a polled query created in React strict mode may not stop polling after the component unmounts while using the cache-and-network fetch policy.

v3.10.3

Compare Source

Patch Changes

v3.10.2

Compare Source

Patch Changes

v3.10.1

Compare Source

Patch Changes

v3.10.0

Compare Source

Minor Changes
Patch Changes

v3.9.11

Compare Source

Patch Changes
  • #​11769 04132af Thanks @​jerelmiller! - Fix an issue where using skipToken or the skip option with useSuspenseQuery in React's strict mode would perform a network request.

v3.9.10

Compare Source

Patch Changes
  • #​11738 b1a5eb8 Thanks @​jerelmiller! - Fix an issue where rerendering useBackgroundQuery after the queryRef had been disposed, either via the auto dispose timeout or by unmounting useReadQuery, would cause the queryRef to be recreated potentially resulting in another network request.

  • #​11738 b1a5eb8 Thanks @​jerelmiller! - Allow queryRefs to be disposed of synchronously when a suspense hook unmounts. This prevents some situations where using a suspense hook with the same query/variables as the disposed queryRef accidentally used the disposed queryRef rather than creating a new instance.

  • #​11670 cc5c03b Thanks @​phryneas! - Bail out of executeSubSelectedArray calls if the array has 0 elements.


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 is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates 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 renovate bot changed the title chore(deps): pin dependency @apollo/client to v3.9.10 chore(deps): pin dependency @apollo/client to v3.9.11 Apr 10, 2024
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 8df16a9 to 4aa8404 Compare April 10, 2024 13:59
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 4aa8404 to 4575918 Compare April 24, 2024 16:24
@renovate renovate bot changed the title chore(deps): pin dependency @apollo/client to v3.9.11 chore(deps): pin dependency @apollo/client to v3.10.0 Apr 24, 2024
@renovate renovate bot changed the title chore(deps): pin dependency @apollo/client to v3.10.0 chore(deps): pin dependency @apollo/client to v3.10.1 Apr 24, 2024
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 4575918 to 3a68ee7 Compare April 24, 2024 20:17
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 3a68ee7 to ae9454c Compare May 3, 2024 18:07
@renovate renovate bot changed the title chore(deps): pin dependency @apollo/client to v3.10.1 chore(deps): pin dependency @apollo/client to v3.10.2 May 3, 2024
@renovate renovate bot changed the title chore(deps): pin dependency @apollo/client to v3.10.2 chore(deps): pin dependency @apollo/client to v3.10.3 May 7, 2024
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from ae9454c to 5d5838f Compare May 7, 2024 17:38
@renovate renovate bot changed the title chore(deps): pin dependency @apollo/client to v3.10.3 chore(deps): pin dependency @apollo/client to v3.10.4 May 15, 2024
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 5d5838f to b8509b3 Compare May 15, 2024 03:53
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from b8509b3 to b9c329c Compare June 12, 2024 20:19
@renovate renovate bot changed the title chore(deps): pin dependency @apollo/client to v3.10.4 chore(deps): pin dependency @apollo/client to v3.10.5 Jun 12, 2024
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from b9c329c to e36ef73 Compare June 21, 2024 14:14
@renovate renovate bot changed the title chore(deps): pin dependency @apollo/client to v3.10.5 chore(deps): pin dependency @apollo/client to v3.10.6 Jun 21, 2024
@renovate renovate bot changed the title chore(deps): pin dependency @apollo/client to v3.10.6 chore(deps): pin dependency @apollo/client to v3.10.7 Jun 26, 2024
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 2 times, most recently from 15edeb5 to e2e0d59 Compare June 27, 2024 21:20
@renovate renovate bot changed the title chore(deps): pin dependency @apollo/client to v3.10.7 chore(deps): pin dependency @apollo/client to v3.10.8 Jun 27, 2024
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from e2e0d59 to b456850 Compare July 23, 2024 01:39
@renovate renovate bot changed the title chore(deps): pin dependency @apollo/client to v3.10.8 chore(deps): pin dependency @apollo/client to v3.11.0 Jul 23, 2024
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from b456850 to 5e541ce Compare July 23, 2024 19:53
@renovate renovate bot changed the title chore(deps): pin dependency @apollo/client to v3.11.0 chore(deps): pin dependency @apollo/client to v3.11.1 Jul 23, 2024
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 5e541ce to 61a69cd Compare July 31, 2024 18:02
@renovate renovate bot changed the title chore(deps): pin dependency @apollo/client to v3.11.1 chore(deps): pin dependency @apollo/client to v3.11.2 Jul 31, 2024
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 61a69cd to 677a736 Compare August 5, 2024 18:23
@renovate renovate bot changed the title chore(deps): pin dependency @apollo/client to v3.11.2 chore(deps): pin dependency @apollo/client to v3.11.3 Aug 5, 2024
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 677a736 to 50eb18a Compare August 7, 2024 22:25
@renovate renovate bot changed the title chore(deps): pin dependency @apollo/client to v3.11.3 chore(deps): pin dependency @apollo/client to v3.11.4 Aug 7, 2024
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 50eb18a to 5dd6914 Compare August 28, 2024 20:13
@renovate renovate bot changed the title chore(deps): pin dependency @apollo/client to v3.11.4 chore(deps): pin dependency @apollo/client to v3.11.5 Aug 28, 2024
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 5dd6914 to 0b1ab67 Compare September 3, 2024 18:11
@renovate renovate bot changed the title chore(deps): pin dependency @apollo/client to v3.11.5 chore(deps): pin dependency @apollo/client to v3.11.6 Sep 3, 2024
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 0b1ab67 to 3e76816 Compare September 4, 2024 19:59
@renovate renovate bot changed the title chore(deps): pin dependency @apollo/client to v3.11.6 chore(deps): pin dependency @apollo/client to v3.11.7 Sep 4, 2024
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 3e76816 to decb570 Compare September 5, 2024 11:07
@renovate renovate bot changed the title chore(deps): pin dependency @apollo/client to v3.11.7 chore(deps): pin dependency @apollo/client to v3.11.8 Sep 5, 2024
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from decb570 to d0281e7 Compare November 7, 2024 18:23
@renovate renovate bot changed the title chore(deps): pin dependency @apollo/client to v3.11.8 chore(deps): pin dependency @apollo/client to v3.11.9 Nov 7, 2024
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from d0281e7 to ad1aa19 Compare November 12, 2024 02:10
@renovate renovate bot changed the title chore(deps): pin dependency @apollo/client to v3.11.9 chore(deps): pin dependency @apollo/client to v3.11.10 Nov 12, 2024
Copy link
Contributor Author

renovate bot commented Nov 12, 2024

⚠️ 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: yarn.lock
node:fs:1363
  const result = binding.mkdir(
                         ^

Error: ENOENT: no such file or directory, mkdir '/home/ubuntu/.cache/node/corepack/v1'
    at mkdirSync (node:fs:1363:26)
    at getTemporaryFolder (/opt/containerbase/tools/corepack/0.29.4/22.11.0/node_modules/corepack/dist/lib/corepack.cjs:21486:27)
    at download (/opt/containerbase/tools/corepack/0.29.4/22.11.0/node_modules/corepack/dist/lib/corepack.cjs:21760:21)
    at installVersion (/opt/containerbase/tools/corepack/0.29.4/22.11.0/node_modules/corepack/dist/lib/corepack.cjs:21854:61)
    at async Engine.ensurePackageManager (/opt/containerbase/tools/corepack/0.29.4/22.11.0/node_modules/corepack/dist/lib/corepack.cjs:22310:32)
    at async Engine.executePackageManagerRequest (/opt/containerbase/tools/corepack/0.29.4/22.11.0/node_modules/corepack/dist/lib/corepack.cjs:22410:25)
    at async Object.runMain (/opt/containerbase/tools/corepack/0.29.4/22.11.0/node_modules/corepack/dist/lib/corepack.cjs:23096:5) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'mkdir',
  path: '/home/ubuntu/.cache/node/corepack/v1'
}

Node.js v22.11.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants