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 dependencies #206

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

fix(deps): update all dependencies #206

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 11, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@apollo/client (source) 3.8.4 -> 3.11.10 age adoption passing confidence
@babel/core (source) 7.23.0 -> 7.26.0 age adoption passing confidence
@babel/runtime-corejs3 (source) 7.23.1 -> 7.26.0 age adoption passing confidence
@commitlint/cli (source) 17.7.1 -> 17.8.1 age adoption passing confidence
@commitlint/config-conventional (source) 17.7.0 -> 17.8.1 age adoption passing confidence
@emotion/react (source) 11.11.1 -> 11.13.5 age adoption passing confidence
@flopflip/types (source) 14.0.1 -> 14.0.2 age adoption passing confidence
@formatjs/cli 6.2.0 -> 6.3.11 age adoption passing confidence
@formatjs/ecma402-abstract 1.17.2 -> 1.18.3 age adoption passing confidence
@formatjs/icu-messageformat-parser (source) 2.6.2 -> 2.9.4 age adoption passing confidence
@formatjs/intl (source) 2.9.3 -> 2.10.15 age adoption passing confidence
@formatjs/intl-displaynames 6.5.2 -> 6.8.5 age adoption passing confidence
@formatjs/intl-listformat 7.4.2 -> 7.7.5 age adoption passing confidence
@graphiql/react (source) 0.17.1 -> 0.27.0 age adoption passing confidence
@graphiql/toolkit (source) 0.8.3 -> 0.11.0 age adoption passing confidence
@manypkg/cli (source) 0.21.0 -> 0.22.0 age adoption passing confidence
@testing-library/cypress 10.0.1 -> 10.0.2 age adoption passing confidence
@types/codemirror (source) 5.60.10 -> 5.60.15 age adoption passing confidence
@types/jest (source) 29.5.5 -> 29.5.14 age adoption passing confidence
@types/lodash (source) 4.14.199 -> 4.17.13 age adoption passing confidence
@types/prop-types (source) 15.7.7 -> 15.7.13 age adoption passing confidence
@types/react (source) 17.0.56 -> 17.0.83 age adoption passing confidence
@types/react-dom (source) 17.0.20 -> 17.0.25 age adoption passing confidence
cypress (source) 13.2.0 -> 13.16.0 age adoption passing confidence
dotenv 16.3.1 -> 16.4.5 age adoption passing confidence
eslint (source) 8.50.0 -> 8.57.1 age adoption passing confidence
graphiql (source) 2.4.1 -> 2.4.7 age adoption passing confidence
graphql 16.8.1 -> 16.9.0 age adoption passing confidence
intl-messageformat 10.5.3 -> 10.7.7 age adoption passing confidence
jest-runner-eslint 2.1.2 -> 2.2.1 age adoption passing confidence
jest-silent-reporter 0.5.0 -> 0.6.0 age adoption passing confidence
prettier (source) 3.0.3 -> 3.3.3 age adoption passing confidence
react-intl (source) 6.4.7 -> 6.8.9 age adoption passing confidence
start-server-and-test 2.0.1 -> 2.0.8 age adoption passing confidence
surge 0.23.1 -> 0.24.6 age adoption passing confidence
typescript (source) 5.0.4 -> 5.6.3 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

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), 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 branch 6 times, most recently from e4bb116 to fde0626 Compare March 19, 2024 10:09
@renovate renovate bot force-pushed the renovate/all branch 8 times, most recently from 1a4fb91 to 26bb36b Compare March 27, 2024 04:41
@renovate renovate bot force-pushed the renovate/all branch 7 times, most recently from a285bdd to a0c7f36 Compare April 6, 2024 07:21
@renovate renovate bot force-pushed the renovate/all branch 2 times, most recently from 21d9a25 to 7670970 Compare April 11, 2024 20:34
@renovate renovate bot force-pushed the renovate/all branch 3 times, most recently from 057ecdb to bf6eb75 Compare April 29, 2024 22:19
@renovate renovate bot force-pushed the renovate/all branch 3 times, most recently from 2b3b4d3 to 0ff108b Compare May 5, 2024 05:20
Copy link
Contributor Author

renovate bot commented May 5, 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: pnpm-lock.yaml
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 35, reused 0, downloaded 19, added 0
Progress: resolved 52, reused 0, downloaded 36, added 0
Progress: resolved 69, reused 0, downloaded 62, added 0
Progress: resolved 91, reused 0, downloaded 71, added 0
Progress: resolved 125, reused 0, downloaded 105, added 0
Progress: resolved 187, reused 0, downloaded 167, added 0
Progress: resolved 253, reused 0, downloaded 234, added 0
Progress: resolved 410, reused 0, downloaded 409, added 0
Progress: resolved 555, reused 0, downloaded 533, added 0
Progress: resolved 646, reused 0, downloaded 623, added 0
Progress: resolved 776, reused 0, downloaded 668, added 0
Progress: resolved 860, reused 0, downloaded 819, added 0
Progress: resolved 958, reused 0, downloaded 918, added 0
Progress: resolved 1073, reused 0, downloaded 1028, added 0
Progress: resolved 1127, reused 0, downloaded 1080, added 0
Progress: resolved 1269, reused 0, downloaded 1231, added 0
Progress: resolved 1420, reused 0, downloaded 1359, added 0
Progress: resolved 1434, reused 0, downloaded 1382, added 0
Progress: resolved 1489, reused 0, downloaded 1392, added 0
Progress: resolved 1492, reused 0, downloaded 1422, added 0
Progress: resolved 1502, reused 0, downloaded 1447, added 0
Progress: resolved 1581, reused 0, downloaded 1529, added 0
Progress: resolved 1637, reused 0, downloaded 1595, added 0
Progress: resolved 1729, reused 0, downloaded 1696, added 0
Progress: resolved 1830, reused 0, downloaded 1795, added 0
undefined
 ERR_PNPM_PATCH_NOT_APPLIED  The following patches were not applied: @graphiql/[email protected]

Either remove them from "patchedDependencies" or update them to match packages in your dependencies.

@renovate renovate bot force-pushed the renovate/all branch 5 times, most recently from 4d3926e to c80b984 Compare October 12, 2024 06:40
@renovate renovate bot force-pushed the renovate/all branch 7 times, most recently from 323810c to 2c05384 Compare October 23, 2024 07:31
@renovate renovate bot force-pushed the renovate/all branch 5 times, most recently from 7b4fb8c to 23e81c8 Compare October 30, 2024 01:51
Copy link
Contributor Author

renovate bot commented Oct 30, 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: pnpm-lock.yaml
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 19, reused 0, downloaded 0, added 0
.                                        |  WARN  deprecated [email protected]
Progress: resolved 68, reused 0, downloaded 0, added 0
Progress: resolved 111, reused 0, downloaded 0, added 0
Progress: resolved 157, reused 0, downloaded 0, added 0
Progress: resolved 208, reused 0, downloaded 0, added 0
Progress: resolved 277, reused 0, downloaded 0, added 0
Progress: resolved 367, reused 0, downloaded 0, added 0
Progress: resolved 463, reused 0, downloaded 0, added 0
Progress: resolved 555, reused 0, downloaded 0, added 0
Progress: resolved 700, reused 0, downloaded 0, added 0
Progress: resolved 769, reused 0, downloaded 0, added 0
Progress: resolved 964, reused 0, downloaded 0, added 0
Progress: resolved 1077, reused 0, downloaded 0, added 0
Progress: resolved 1186, reused 0, downloaded 0, added 0
Progress: resolved 1391, reused 0, downloaded 0, added 0
Progress: resolved 1467, reused 0, downloaded 0, added 0
Progress: resolved 1674, reused 0, downloaded 0, added 0
Progress: resolved 1937, reused 0, downloaded 0, added 0
undefined
 ERR_PNPM_PATCH_NOT_APPLIED  The following patches were not applied: @graphiql/[email protected]

Either remove them from "patchedDependencies" or update them to match packages in your dependencies.

@renovate renovate bot force-pushed the renovate/all branch 6 times, most recently from fa110b4 to a16ebb9 Compare November 9, 2024 19:37
@renovate renovate bot force-pushed the renovate/all branch 3 times, most recently from aabe542 to 1ff1dfc Compare November 18, 2024 08:05
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