Skip to content

fix(deps): update all non-major dependencies #932

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(deps): update all non-major dependencies #932

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 13, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@apollo/client (source) 3.12.11 -> 3.13.7 age adoption passing confidence
@babel/core (source) 7.26.8 -> 7.26.10 age adoption passing confidence
@babel/preset-env (source) 7.26.8 -> 7.26.9 age adoption passing confidence
@graphql-mesh/apollo-link (source) ^0.105.0 -> ^0.106.0 age adoption passing confidence
@graphql-mesh/cli (source) ^0.98.0 -> ^0.100.0 age adoption passing confidence
@graphql-mesh/fusion-runtime (source) ^0.10.0 -> ^0.11.0 age adoption passing confidence
@graphql-mesh/graphql (source) ^0.103.0 -> ^0.104.0 age adoption passing confidence
@graphql-mesh/transform-prefix (source) ^0.103.0 -> ^0.105.0 age adoption passing confidence
@graphql-mesh/transform-rename (source) ^0.103.0 -> ^0.105.0 age adoption passing confidence
@graphql-mesh/transform-type-merging (source) ^0.103.0 -> ^0.104.0 age adoption passing confidence
@graphql-mesh/types (source) ^0.78.0 || ^0.79.0 || ^0.80.0 || ^0.81.0 || ^0.82.0 || ^0.83.0 || ^0.84.0 || ^0.85.0 || ^0.89.0 || ^0.90.0 || ^0.91.0 || ^0.93.0 || ^0.94.0 || ^0.97.0 || ^0.98.0 || ^0.99.0 || ^0.100.0 || ^0.101.0 || ^0.102.0 || ^0.103.0 -> ^0.78.0 || ^0.79.0 || ^0.80.0 || ^0.81.0 || ^0.82.0 || ^0.83.0 || ^0.84.0 || ^0.85.0 || ^0.89.0 || ^0.90.0 || ^0.91.0 || ^0.93.0 || ^0.94.0 || ^0.97.0 || ^0.98.0 || ^0.99.0 || ^0.100.0 || ^0.101.0 || ^0.102.0 || ^0.103.0 || ^0.104.0 age adoption passing confidence
@graphql-mesh/urql-exchange (source) ^0.105.0 -> ^0.106.0 age adoption passing confidence
@graphql-tools/utils (source) 10.8.1 -> 10.8.6 age adoption passing confidence
@tanstack/react-query (source) 5.66.0 -> 5.74.3 age adoption passing confidence
@types/lodash (source) 4.17.15 -> 4.17.16 age adoption passing confidence
@types/node (source) 22.13.2 -> 22.14.1 age adoption passing confidence
@types/react (source) 19.0.8 -> 19.1.2 age adoption passing confidence
@types/react-dom (source) 19.0.3 -> 19.1.2 age adoption passing confidence
@vitejs/plugin-react (source) 4.3.4 -> 4.4.0 age adoption passing confidence
eslint (source) 9.20.1 -> 9.24.0 age adoption passing confidence
prettier (source) 3.5.0 -> 3.5.3 age adoption passing confidence
pretty-quick 4.0.0 -> 4.1.1 age adoption passing confidence
react (source) 19.0.0 -> 19.1.0 age adoption passing confidence
react-dom (source) 19.0.0 -> 19.1.0 age adoption passing confidence
ts-jest (source) 29.2.5 -> 29.3.2 age adoption passing confidence
urql (source) 4.2.1 -> 4.2.2 age adoption passing confidence
vite (source) 6.1.0 -> 6.3.0 age adoption passing confidence

Release Notes

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

v3.13.7

Compare Source

Patch Changes

v3.13.6

Compare Source

Patch Changes

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

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

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.

babel/babel (@​babel/core)

v7.26.10

Compare Source

👓 Spec Compliance
🐛 Bug Fix
💅 Polish
🏠 Internal

v7.26.9

Compare Source

🐛 Bug Fix
🏠 Internal
ardatan/graphql-mesh (@​graphql-mesh/apollo-link)

v0.106.3

Compare Source

Patch Changes

v0.106.2

Compare Source

Patch Changes

v0.106.1

Compare Source

Patch Changes

v0.106.0

Compare Source

Patch Changes

v0.105.23

Compare Source

Patch Changes

v0.105.22

Compare Source

Patch Changes

v0.105.21

Compare Source

Patch Changes

v0.105.20

Compare Source

Patch Changes

v0.105.19

Compare Source

Patch Changes

v0.105.18

Compare Source

Patch Changes
ardatan/graphql-mesh (@​graphql-mesh/cli)

v0.100.4

Compare Source

Patch Changes

v0.100.3

Compare Source

Patch Changes

v0.100.2

Compare Source

Patch Changes

v0.100.1

Compare Source

Patch Changes

v0.100.0

Compare Source

Patch Changes

v0.99.2

Compare Source

Patch Changes

v0.99.1

Compare Source

Patch Changes

v0.99.0

Compare Source

Patch Changes

v0.98.27

Compare Source

Patch Changes

v0.98.26

Compare Source

Patch Changes

v0.98.25

Compare Source

Patch Changes

Configuration

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

🚦 Automerge: Enabled.

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

@changeset-bot changeset-bot
Copy link

changeset-bot bot commented Feb 13, 2025 •
edited
Loading

⚠️ No Changeset found

Latest commit: 6ce9b20

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 11 times, most recently from 7848480 to fe8c78e Compare February 19, 2025 12:27
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 11 times, most recently from 68cbb30 to a62a3c5 Compare February 27, 2025 06:14
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 31a741c to 3235f2f Compare March 3, 2025 17:25
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 12 times, most recently from 3ba09b0 to db72d2a Compare April 5, 2025 06:07
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 12 times, most recently from 1e62c09 to 45b8555 Compare April 13, 2025 18:05
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 3256557 to dc3e783 Compare April 15, 2025 10:31
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from dc3e783 to 6ce9b20 Compare April 16, 2025 08:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants