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 #3639

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

fix(deps): update all dependencies #3639

wants to merge 2 commits into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 18, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@apollo/client (source) 3.7.14 -> 3.11.10 age adoption passing confidence
@changesets/cli (source) 2.27.5 -> 2.27.10 age adoption passing confidence
@formatjs/cli 6.2.12 -> 6.3.11 age adoption passing confidence
@formatjs/icu-messageformat-parser (source) 2.7.8 -> 2.9.4 age adoption passing confidence
@manypkg/cli (source) 0.21.4 -> 0.22.0 age adoption passing confidence
@manypkg/find-root (source) 2.2.1 -> 2.2.3 age adoption passing confidence
@preconstruct/cli (source) 2.6.2 -> 2.8.10 age adoption passing confidence
@rollup/plugin-graphql (source) 2.0.4 -> 2.0.5 age adoption passing confidence
@rollup/pluginutils (source) 5.1.0 -> 5.1.3 age adoption passing confidence
@sentry/browser (source) 7.119.1 -> 7.120.0 age adoption passing confidence
@sentry/react (source) 7.117.0 -> 7.120.0 age adoption passing confidence
@sentry/types (source) 7.117.0 -> 7.120.0 age adoption passing confidence
@types/jscodeshift (source) 0.11.11 -> 0.12.0 age adoption passing confidence
@types/node-fetch (source) 2.6.11 -> 2.6.12 age adoption passing confidence
@vitejs/plugin-react (source) 4.3.1 -> 4.3.3 age adoption passing confidence
@vitejs/plugin-react-swc 3.7.0 -> 3.7.1 age adoption passing confidence
ajv (source) 8.16.0 -> 8.17.1 age adoption passing confidence
babel-loader 8.3.0 -> 8.4.1 age adoption passing confidence
cldr 7.5.0 -> 7.6.0 age adoption passing confidence
eslint (source) 8.57.0 -> 8.57.1 age adoption passing confidence
express (source) 4.20.0 -> 4.21.1 age adoption passing confidence
graphql 16.8.2 -> 16.9.0 age adoption passing confidence
html-webpack-plugin 5.6.0 -> 5.6.3 age adoption passing confidence
jest-runner-eslint 2.2.0 -> 2.2.1 age adoption passing confidence
jscodeshift 0.15.2 -> 0.16.1 age adoption passing confidence
logform 2.6.0 -> 2.7.0 age adoption passing confidence
mini-css-extract-plugin 2.9.0 -> 2.9.2 age adoption passing confidence
pnpm (source) 8.15.8 -> 8.15.9 age adoption passing confidence
postcss (source) 8.4.38 -> 8.4.49 age adoption passing confidence
react-select (source) 5.8.0 -> 5.8.3 age adoption passing confidence
rimraf 5.0.7 -> 5.0.10 age adoption passing confidence
semver 7.6.2 -> 7.6.3 age adoption passing confidence
serve-handler 6.1.5 -> 6.1.6 age adoption passing confidence
start-server-and-test 2.0.4 -> 2.0.8 age adoption passing confidence
typescript (source) 5.0.4 -> 5.6.3 age adoption passing confidence
uglify-js 3.18.0 -> 3.19.3 age adoption passing confidence
vite-bundle-analyzer 0.12.1 -> 0.13.1 age adoption passing confidence
webpack 5.94.0 -> 5.96.1 age adoption passing confidence
winston 3.13.0 -> 3.17.0 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

[Compar


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 requested a review from a team as a code owner November 18, 2024 01:37
@renovate renovate bot added the 🤖 Type: Dependencies Dependency updates or something similar label Nov 18, 2024
Copy link
Contributor Author

renovate bot commented Nov 18, 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
application-templates/starter            |  WARN  The field "resolutions" was found in /tmp/renovate/repos/github/commercetools/merchant-center-application-kit/application-templates/starter/package.json. This will not take effect. You should configure "resolutions" at the root of the workspace instead.
application-templates/starter-typescript |  WARN  The field "resolutions" was found in /tmp/renovate/repos/github/commercetools/merchant-center-application-kit/application-templates/starter-typescript/package.json. This will not take effect. You should configure "resolutions" at the root of the workspace instead.
custom-views-templates/starter           |  WARN  The field "resolutions" was found in /tmp/renovate/repos/github/commercetools/merchant-center-application-kit/custom-views-templates/starter/package.json. This will not take effect. You should configure "resolutions" at the root of the workspace instead.
.../starter-typescript                   |  WARN  The field "resolutions" was found in /tmp/renovate/repos/github/commercetools/merchant-center-application-kit/custom-views-templates/starter-typescript/package.json. This will not take effect. You should configure "resolutions" at the root of the workspace instead.
Scope: all 37 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
application-templates/starter            |  WARN  deprecated [email protected]
Progress: resolved 7, reused 0, downloaded 1, added 0
Progress: resolved 48, reused 0, downloaded 42, added 0
Progress: resolved 80, reused 0, downloaded 74, added 0
Progress: resolved 106, reused 0, downloaded 100, added 0
Progress: resolved 164, reused 0, downloaded 158, added 0
Progress: resolved 182, reused 0, downloaded 176, added 0
Progress: resolved 191, reused 0, downloaded 185, added 0
Progress: resolved 227, reused 0, downloaded 221, added 0
Progress: resolved 264, reused 0, downloaded 258, added 0
Progress: resolved 270, reused 0, downloaded 264, added 0
.                                        |  WARN  deprecated [email protected]
Progress: resolved 312, reused 0, downloaded 307, added 0
Progress: resolved 312, reused 0, downloaded 310, added 0
Progress: resolved 321, reused 0, downloaded 317, added 0
Progress: resolved 330, reused 0, downloaded 322, added 0
Progress: resolved 335, reused 0, downloaded 322, added 0
Progress: resolved 340, reused 0, downloaded 322, added 0
Progress: resolved 340, reused 0, downloaded 323, added 0
Progress: resolved 360, reused 0, downloaded 360, added 0
Progress: resolved 389, reused 0, downloaded 374, added 0
Progress: resolved 423, reused 0, downloaded 409, added 0
Progress: resolved 482, reused 0, downloaded 469, added 0
Progress: resolved 553, reused 0, downloaded 540, added 0
Progress: resolved 626, reused 0, downloaded 613, added 0
Progress: resolved 717, reused 0, downloaded 704, added 0
Progress: resolved 776, reused 0, downloaded 763, added 0
Progress: resolved 862, reused 0, downloaded 850, added 0
Progress: resolved 968, reused 0, downloaded 957, added 0
Progress: resolved 1016, reused 0, downloaded 1005, added 0
Progress: resolved 1099, reused 0, downloaded 1089, added 0
Progress: resolved 1147, reused 0, downloaded 1146, added 0
Progress: resolved 1240, reused 0, downloaded 1239, added 0
Progress: resolved 1338, reused 0, downloaded 1337, added 0
Progress: resolved 1425, reused 0, downloaded 1414, added 0
Progress: resolved 1473, reused 0, downloaded 1454, added 0
Progress: resolved 1523, reused 0, downloaded 1507, added 0
Progress: resolved 1570, reused 0, downloaded 1544, added 0
Progress: resolved 1625, reused 0, downloaded 1600, added 0
Progress: resolved 1677, reused 0, downloaded 1653, added 0
Progress: resolved 1722, reused 0, downloaded 1661, added 0
Progress: resolved 1726, reused 0, downloaded 1661, added 0
Progress: resolved 1750, reused 0, downloaded 1728, added 0
Progress: resolved 1786, reused 0, downloaded 1745, added 0
Progress: resolved 1819, reused 0, downloaded 1791, added 0
Progress: resolved 1859, reused 0, downloaded 1824, added 0
Progress: resolved 1870, reused 0, downloaded 1838, added 0
Progress: resolved 1896, reused 0, downloaded 1838, added 0
Progress: resolved 1916, reused 0, downloaded 1839, added 0
Progress: resolved 1930, reused 0, downloaded 1839, added 0
Progress: resolved 1944, reused 0, downloaded 1843, added 0
Progress: resolved 1968, reused 0, downloaded 1898, added 0
Progress: resolved 1991, reused 0, downloaded 1912, added 0
Progress: resolved 2038, reused 0, downloaded 1963, added 0
Progress: resolved 2088, reused 0, downloaded 2003, added 0
Progress: resolved 2114, reused 0, downloaded 2043, added 0
Progress: resolved 2159, reused 0, downloaded 2087, added 0
Progress: resolved 2218, reused 0, downloaded 2146, added 0
Progress: resolved 2279, reused 0, downloaded 2208, added 0
Progress: resolved 2332, reused 0, downloaded 2246, added 0
Progress: resolved 2400, reused 0, downloaded 2311, added 0
Progress: resolved 2433, reused 0, downloaded 2347, added 0
Progress: resolved 2505, reused 0, downloaded 2414, added 0
Progress: resolved 2534, reused 0, downloaded 2449, added 0
Progress: resolved 2588, reused 0, downloaded 2514, added 0
Progress: resolved 2666, reused 0, downloaded 2613, added 0
Progress: resolved 2745, reused 0, downloaded 2692, added 0
Progress: resolved 2820, reused 0, downloaded 2766, added 0
 ERR_PNPM_PATCH_NOT_APPLIED  The following patches were not applied: [email protected]

Either remove them from "patchedDependencies" or update them to match packages in your dependencies.
Progress: resolved 2857, reused 0, downloaded 2806, added 0

Copy link

vercel bot commented Nov 18, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
mc-app-kit-playground ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 20, 2024 1:18pm
merchant-center-application-kit-components-playground ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 20, 2024 1:18pm

Copy link

changeset-bot bot commented Nov 18, 2024

⚠️ No Changeset found

Latest commit: 7c991ac

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

Comment on lines +9 to +10
-declare function adapter(userPlugin: Plugin): Plugin$1<any>;
+declare function adapter(userPlugin: Plugin): Plugin$1;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@CarlosCortizasCT Can you check / confirm that this was the actual patch?

Copy link
Contributor Author

renovate bot commented Nov 20, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🤖 Type: Dependencies Dependency updates or something similar
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant