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): update all non-major dependencies #598

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 1, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@apollo/client (source) ^3.9.5 -> ^3.11.10 age adoption passing confidence
@nuxt-themes/docus ^1.1.3 -> ^1.15.1 age adoption passing confidence
@nuxt/kit (source) ^3.10.3 -> ^3.14.159 age adoption passing confidence
@nuxt/module-builder ^0.5.5 -> ^0.8.4 age adoption passing confidence
@nuxt/schema (source) ^3.10.3 -> ^3.14.159 age adoption passing confidence
@nuxt/ui (source) ^2.14.1 -> ^2.19.2 age adoption passing confidence
@rollup/plugin-graphql (source) ^2.0.4 -> ^2.0.5 age adoption passing confidence
@types/node (source) ^20.11.24 -> ^20.17.6 age adoption passing confidence
@vue/apollo-composable (source) ^4.0.1 -> ^4.2.1 age adoption passing confidence
@vue/apollo-option (source) ^4.0.0 -> ^4.2.0 age adoption passing confidence
eslint (source) ^8.57.0 -> ^8.57.1 age adoption passing confidence
graphql ^16.8.1 -> ^16.9.0 age adoption passing confidence
graphql-ws ^5.15.0 -> ^5.16.0 age adoption passing confidence
jiti ^1.21.0 -> ^1.21.6 age adoption passing confidence
nuxt (source) ^3.10.3 -> ^3.14.159 age adoption passing confidence
nuxt (source) ^3.0.0 -> ^3.14.159 age adoption passing confidence
ohash ^1.1.3 -> ^1.1.4 age adoption passing confidence
pnpm (source) 8.15.2 -> 8.15.9 age adoption passing confidence
yarn 1.22.19 -> 1.22.22 age adoption passing confidence

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.

v3.9.9

Compare Source

Patch Changes
  • #​11696 466ef82 Thanks @​PiR1! - Immediately dispose of the queryRef if useBackgroundQuery unmounts before the auto dispose timeout kicks in.

v3.9.8

Compare Source

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.

👻 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.

Copy link

netlify bot commented Mar 1, 2024

Deploy Preview for apollo-module failed. Why did it fail? →

Name Link
🔨 Latest commit ebac958
🔍 Latest deploy log https://app.netlify.com/sites/apollo-module/deploys/6732afe1f1195700088827e7

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from d077e40 to 3dff029 Compare March 12, 2024 02:46
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from b9b945b to 0df96a8 Compare March 19, 2024 13:19
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 2153107 to 2f97b4f Compare March 26, 2024 15:25
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 425b151 to 3359e9c Compare April 2, 2024 21:17
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from a1331ec to f5bdd05 Compare April 10, 2024 15:18
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 18e9d9a to d577260 Compare April 13, 2024 20:22
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 78b6b1a to ac4624c Compare September 23, 2024 10:57
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from aaa89a8 to 73f6ca0 Compare September 27, 2024 18:57
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 4243bfe to e7aea09 Compare October 9, 2024 15:02
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 04937b8 to 0d752b3 Compare October 23, 2024 15:42
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from e0fe6ae to d5a9bb1 Compare October 31, 2024 20:20
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from 36e8dbb to 3c0d40d Compare November 7, 2024 19:29
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.

0 participants