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

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

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 11, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@apollo/client (source) 3.8.10 -> 3.11.8 age adoption passing confidence
@emotion/react (source) 11.11.3 -> 11.13.3 age adoption passing confidence
@emotion/styled (source) 11.11.0 -> 11.13.0 age adoption passing confidence
@sentry/react (source) 7.93.0 -> 7.119.0 age adoption passing confidence
@sentry/tracing (source) 7.93.0 -> 7.114.0 age adoption passing confidence
@tanstack/react-query (source) 5.35.1 -> 5.59.0 age adoption passing confidence
@types/lodash (source) 4.14.202 -> 4.17.9 age adoption passing confidence
@types/react (source) 18.2.48 -> 18.3.11 age adoption passing confidence
@types/react-dom (source) 18.2.18 -> 18.3.0 age adoption passing confidence
@types/react-simple-maps (source) 3.0.4 -> 3.0.6 age adoption passing confidence
@types/react-syntax-highlighter (source) 15.5.11 -> 15.5.13 age adoption passing confidence
chart.js (source) 4.4.1 -> 4.4.4 age adoption passing confidence
date-fns 3.2.0 -> 3.6.0 age adoption passing confidence
eslint (source) 8.56.0 -> 8.57.1 age adoption passing confidence
eslint-plugin-react-hooks (source) 4.6.0 -> 4.6.2 age adoption passing confidence
eslint-plugin-react-refresh 0.4.5 -> 0.4.12 age adoption passing confidence
graphql 16.8.1 -> 16.9.0 age adoption passing confidence
husky 9.0.11 -> 9.1.6 age adoption passing confidence
pnpm (source) 8.15.1 -> 8.15.9 age adoption passing confidence
prettier (source) 3.2.4 -> 3.3.3 age adoption passing confidence
react (source) 18.2.0 -> 18.3.1 age adoption passing confidence
react-countdown 2.3.5 -> 2.3.6 age adoption passing confidence
react-dom (source) 18.2.0 -> 18.3.1 age adoption passing confidence
react-hook-form (source) 7.49.3 -> 7.53.0 age adoption passing confidence
react-intersection-observer 9.5.3 -> 9.13.1 age adoption passing confidence
react-loading-skeleton 3.3.1 -> 3.5.0 age adoption passing confidence
react-number-format (source) 5.3.1 -> 5.4.2 age adoption passing confidence
react-router-dom (source) 6.21.3 -> 6.26.2 age adoption passing confidence
recharts 2.10.4 -> 2.12.7 age adoption passing confidence
statsig-react 1.34.0 -> 1.38.1 age adoption passing confidence
typescript (source) 5.3.3 -> 5.6.2 age adoption passing confidence
vitest (source) 2.1.1 -> 2.1.2 age adoption passing confidence

Release Notes

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

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

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 renovate bot force-pushed the renovate/all-minor-patch branch 10 times, most recently from 97ee872 to f6e3e00 Compare May 17, 2024 18:32
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from 242f9ae to 5ac87ca Compare May 23, 2024 22:52
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 11 times, most recently from 128032c to a5da7f3 Compare May 31, 2024 10:16
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from 5bee1de to ff85ef2 Compare September 14, 2024 11:38
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 8 times, most recently from bed1370 to a6f84d3 Compare September 21, 2024 19:30
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 2763158 to 2b013db Compare September 29, 2024 22:27
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 8386b55 to cfd4cc8 Compare October 2, 2024 18:54
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from cfd4cc8 to 6ebfc97 Compare October 2, 2024 20:56
@gregnazario
Copy link
Contributor

Closing, no plans to do this atm, only one left was pnpm

@gregnazario gregnazario closed this Oct 2, 2024
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.

1 participant