Skip to content

Update react monorepo#117

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/react-monorepo
Open

Update react monorepo#117
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/react-monorepo

Conversation

@renovate
Copy link

@renovate renovate bot commented Mar 26, 2021

This PR contains the following updates:

Package Change Age Confidence
@types/react (source) 17.0.1917.0.91 age confidence
@types/react-dom (source) 17.0.917.0.26 age confidence
react (source) 17.0.117.0.2 age confidence
react-dom (source) 17.0.117.0.2 age confidence

Release Notes

facebook/react (react)

v17.0.2

Compare Source

React DOM

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone Asia/Tokyo, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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
Copy link
Author

renovate bot commented Mar 26, 2021

⚠️ 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 check 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: package-lock.json
npm WARN old lockfile 
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile 
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! Found: @capacitor/core@2.4.7
npm ERR! node_modules/@capacitor/core
npm ERR!   @capacitor/core@"2.4.7" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @capacitor/core@"~1.3.0" from @ionic/react-hooks@0.0.8
npm ERR! node_modules/@ionic/react-hooks
npm ERR!   @ionic/react-hooks@"0.0.8" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2021-04-19T15_40_51_037Z-debug.log

@renovate renovate bot force-pushed the renovate/react-monorepo branch from de2e710 to dca7cd3 Compare April 19, 2021 15:41
@renovate renovate bot force-pushed the renovate/react-monorepo branch from dca7cd3 to 567cd4a Compare May 7, 2021 16:43
@renovate
Copy link
Author

renovate bot commented May 7, 2021

⚠️ 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: package-lock.json
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: ionic-react-wordpress@0.0.1
npm WARN Found: react@17.0.1
npm WARN node_modules/react
npm WARN   react@"17.0.2" from the root project
npm WARN   9 more (@ionic/react, @ionic/react-router, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.6" from @ionic/react-hooks@0.0.8
npm WARN node_modules/@ionic/react-hooks
npm WARN   @ionic/react-hooks@"0.0.8" from the root project
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: ionic-react-wordpress@0.0.1
npm WARN Found: react@17.0.1
npm WARN node_modules/react
npm WARN   react@"17.0.2" from the root project
npm WARN   9 more (@ionic/react, @ionic/react-router, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"17.0.1" from react-dom@17.0.1
npm WARN node_modules/react-dom
npm WARN   react-dom@"17.0.2" from the root project
npm WARN   3 more (@ionic/react, @ionic/react-router, @testing-library/react)
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: ionic-react-wordpress@0.0.1
npm WARN Found: react@17.0.1
npm WARN node_modules/react
npm WARN   react@"17.0.2" from the root project
npm WARN   9 more (@ionic/react, @ionic/react-router, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"17.0.1" from react-dom@17.0.1
npm WARN node_modules/react-dom
npm WARN   react-dom@"17.0.2" from the root project
npm WARN   3 more (@ionic/react, @ionic/react-router, @testing-library/react)
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: ionic-react-wordpress@0.0.1
npm WARN Found: react@17.0.1
npm WARN node_modules/react
npm WARN   react@"17.0.2" from the root project
npm WARN   9 more (@ionic/react, @ionic/react-router, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"17.0.1" from react-dom@17.0.1
npm WARN node_modules/react-dom
npm WARN   react-dom@"17.0.2" from the root project
npm WARN   3 more (@ionic/react, @ionic/react-router, @testing-library/react)
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @ionic/react-hooks@0.0.8
npm ERR! Found: @capacitor/core@2.4.7
npm ERR! node_modules/@capacitor/core
npm ERR!   @capacitor/core@"2.4.7" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @capacitor/core@"~1.3.0" from @ionic/react-hooks@0.0.8
npm ERR! node_modules/@ionic/react-hooks
npm ERR!   @ionic/react-hooks@"0.0.8" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @capacitor/core@1.3.0
npm ERR! node_modules/@capacitor/core
npm ERR!   peer @capacitor/core@"~1.3.0" from @ionic/react-hooks@0.0.8
npm ERR!   node_modules/@ionic/react-hooks
npm ERR!     @ionic/react-hooks@"0.0.8" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-03-05T14_06_34_332Z-debug-0.log

@renovate renovate bot force-pushed the renovate/react-monorepo branch 7 times, most recently from ea91d58 to b5bc9ec Compare May 14, 2021 16:26
@renovate renovate bot force-pushed the renovate/react-monorepo branch 4 times, most recently from 0375903 to c3eac91 Compare May 21, 2021 18:35
@renovate renovate bot force-pushed the renovate/react-monorepo branch 4 times, most recently from 5452b48 to 3006c43 Compare May 28, 2021 21:23
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 3006c43 to 0decbdc Compare June 4, 2021 16:55
@renovate
Copy link
Author

renovate bot commented Jun 4, 2021

⚠ 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: package-lock.json
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: ionic-react-wordpress@0.0.1
npm WARN Found: react@17.0.1
npm WARN node_modules/react
npm WARN   react@"17.0.2" from the root project
npm WARN   9 more (@ionic/react, @ionic/react-router, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.6" from @ionic/react-hooks@0.0.8
npm WARN node_modules/@ionic/react-hooks
npm WARN   @ionic/react-hooks@"0.0.8" from the root project
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: ionic-react-wordpress@0.0.1
npm WARN Found: react@17.0.1
npm WARN node_modules/react
npm WARN   react@"17.0.2" from the root project
npm WARN   9 more (@ionic/react, @ionic/react-router, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"17.0.1" from react-dom@17.0.1
npm WARN node_modules/react-dom
npm WARN   react-dom@"17.0.2" from the root project
npm WARN   3 more (@ionic/react, @ionic/react-router, @testing-library/react)
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: ionic-react-wordpress@0.0.1
npm WARN Found: react@17.0.1
npm WARN node_modules/react
npm WARN   react@"17.0.2" from the root project
npm WARN   9 more (@ionic/react, @ionic/react-router, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"17.0.1" from react-dom@17.0.1
npm WARN node_modules/react-dom
npm WARN   react-dom@"17.0.2" from the root project
npm WARN   3 more (@ionic/react, @ionic/react-router, @testing-library/react)
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: ionic-react-wordpress@0.0.1
npm WARN Found: react@17.0.1
npm WARN node_modules/react
npm WARN   react@"17.0.2" from the root project
npm WARN   9 more (@ionic/react, @ionic/react-router, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"17.0.1" from react-dom@17.0.1
npm WARN node_modules/react-dom
npm WARN   react-dom@"17.0.2" from the root project
npm WARN   3 more (@ionic/react, @ionic/react-router, @testing-library/react)
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @ionic/react-hooks@0.0.8
npm ERR! Found: @capacitor/core@2.4.7
npm ERR! node_modules/@capacitor/core
npm ERR!   @capacitor/core@"2.4.7" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @capacitor/core@"~1.3.0" from @ionic/react-hooks@0.0.8
npm ERR! node_modules/@ionic/react-hooks
npm ERR!   @ionic/react-hooks@"0.0.8" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @capacitor/core@1.3.0
npm ERR! node_modules/@capacitor/core
npm ERR!   peer @capacitor/core@"~1.3.0" from @ionic/react-hooks@0.0.8
npm ERR!   node_modules/@ionic/react-hooks
npm ERR!     @ionic/react-hooks@"0.0.8" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-03-26T11_28_33_867Z-debug-0.log

@renovate renovate bot force-pushed the renovate/react-monorepo branch 4 times, most recently from cc8702f to 1931a41 Compare June 11, 2021 16:38
@renovate renovate bot force-pushed the renovate/react-monorepo branch 3 times, most recently from c912f78 to 148e893 Compare June 18, 2021 16:15
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 148e893 to 4c39c30 Compare June 25, 2021 16:12
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 4c39c30 to c7762b1 Compare July 2, 2021 16:58
@renovate renovate bot force-pushed the renovate/react-monorepo branch 3 times, most recently from bdc42f2 to cce194b Compare August 20, 2021 17:14
@renovate renovate bot force-pushed the renovate/react-monorepo branch 3 times, most recently from 7801610 to 9362b4d Compare August 27, 2021 17:40
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 9362b4d to 36a7eea Compare August 28, 2021 00:54
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 36a7eea to ced49aa Compare March 17, 2023 01:52
@renovate renovate bot changed the title Update react monorepo to v17.0.2 Update react monorepo Mar 17, 2023
@renovate renovate bot force-pushed the renovate/react-monorepo branch 2 times, most recently from 6cbab44 to 9ae5a1d Compare March 29, 2023 23:59
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 9ae5a1d to 75fb7c7 Compare April 17, 2023 10:13
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 75fb7c7 to b448f77 Compare May 28, 2023 11:55
@renovate renovate bot force-pushed the renovate/react-monorepo branch 2 times, most recently from 9749ae5 to 385bc9c Compare June 13, 2023 16:32
@renovate renovate bot force-pushed the renovate/react-monorepo branch 2 times, most recently from cbc809a to ea6d27e Compare August 9, 2023 19:47
@renovate renovate bot force-pushed the renovate/react-monorepo branch from ea6d27e to 4ab2c82 Compare August 22, 2023 19:15
@renovate renovate bot force-pushed the renovate/react-monorepo branch 3 times, most recently from 8bc4640 to c74a8d6 Compare October 1, 2023 10:30
@renovate renovate bot force-pushed the renovate/react-monorepo branch from c74a8d6 to 23785c0 Compare October 10, 2023 22:21
@renovate renovate bot force-pushed the renovate/react-monorepo branch 2 times, most recently from 9732058 to 0c53b4b Compare October 18, 2023 20:17
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 0c53b4b to c7756d1 Compare November 7, 2023 21:24
@renovate renovate bot force-pushed the renovate/react-monorepo branch 2 times, most recently from f48a40f to 23fad8c Compare November 22, 2023 02:19
@renovate renovate bot force-pushed the renovate/react-monorepo branch 2 times, most recently from 840d85a to 6684a84 Compare December 13, 2023 04:30
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