Skip to content

fix(deps): update react monorepo to v18 (major)#530

Open
renovate[bot] wants to merge 2 commits intomasterfrom
renovate/major-react-monorepo
Open

fix(deps): update react monorepo to v18 (major)#530
renovate[bot] wants to merge 2 commits intomasterfrom
renovate/major-react-monorepo

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Oct 11, 2021

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
react (source) 16.14.0 -> 18.2.0 age adoption passing confidence
react-dom (source) 16.14.0 -> 18.2.0 age adoption passing confidence
react-test-renderer (source) 16.14.0 -> 18.2.0 age adoption passing confidence

Configuration

📅 Schedule: Branch creation - "before 3am on Monday" in timezone America/New_York, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot requested a review from a team October 11, 2021 04:07
@codecov-commenter
Copy link
Copy Markdown

codecov-commenter commented Oct 11, 2021

Codecov Report

Merging #530 (5030b57) into master (32cc2c7) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #530   +/-   ##
=======================================
  Coverage   40.80%   40.80%           
=======================================
  Files         107      107           
  Lines        2240     2240           
  Branches      608      608           
=======================================
  Hits          914      914           
  Misses       1242     1242           
  Partials       84       84           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 32cc2c7...5030b57. Read the comment docs.

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from ae1addf to 7b52677 Compare October 14, 2021 19:51
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 7 times, most recently from 8b9f7ca to 6eefe03 Compare October 25, 2021 09:31
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 6 times, most recently from 7cecce0 to 70766d4 Compare November 1, 2021 18:07
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from b3109b8 to cb47127 Compare November 8, 2021 11:37
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 40de2a7 to 0da904b Compare November 15, 2021 11:17
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 6 times, most recently from 7d7b053 to 191d3e3 Compare November 29, 2021 09:12
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 8a50dff to bacd7bd Compare December 7, 2021 17:27
@renovate renovate bot changed the title fix(deps): update react monorepo to v17 (major) fix(deps): update react monorepo to v18 (major) Mar 29, 2022
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from c14c97b to b81c0cf Compare April 8, 2022 11:13
@renovate
Copy link
Copy Markdown
Contributor Author

renovate bot commented Apr 8, 2022

⚠ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @edx/frontend-build@12.3.0
npm ERR! Found: react@18.2.0
npm ERR! node_modules/react
npm ERR!   react@"18.2.0" from the root project
npm ERR!   peer react@">=16.3" from @fortawesome/react-fontawesome@0.2.0
npm ERR!   node_modules/@edx/frontend-component-footer/node_modules/@fortawesome/react-fontawesome
npm ERR!     @fortawesome/react-fontawesome@"0.2.0" from @edx/frontend-component-footer@11.2.1
npm ERR!     node_modules/@edx/frontend-component-footer
npm ERR!       @edx/frontend-component-footer@"11.2.1" from the root project
npm ERR!   31 more (@fortawesome/react-fontawesome, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.9.0 || ^17.0.0" from @edx/frontend-build@12.3.0
npm ERR! node_modules/@edx/frontend-build
npm ERR!   dev @edx/frontend-build@"12.3.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: react@17.0.2
npm ERR! node_modules/react
npm ERR!   peer react@"^16.9.0 || ^17.0.0" from @edx/frontend-build@12.3.0
npm ERR!   node_modules/@edx/frontend-build
npm ERR!     dev @edx/frontend-build@"12.3.0" 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/2022-10-24T14_31_08_414Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from b81c0cf to e2e0368 Compare April 10, 2022 22:41
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from e2e0368 to fadee9e Compare April 26, 2022 21:14
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 86db8a4 to 765674b Compare May 9, 2022 20:19
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 765674b to 51ba5c5 Compare May 16, 2022 22:12
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 51ba5c5 to 5d26d2e Compare May 24, 2022 10:37
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 5d26d2e to 576eebd Compare June 14, 2022 20:33
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 576eebd to e5178f4 Compare June 29, 2022 10:59
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 4 times, most recently from 0d298f2 to a8654a6 Compare July 28, 2022 06:40
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 4 times, most recently from 7ce969b to e149388 Compare August 9, 2022 17:51
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 6 times, most recently from 865eb62 to 938437e Compare August 19, 2022 15:53
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 938437e to 8f0cf2f Compare August 21, 2022 23:07
@renovate
Copy link
Copy Markdown
Contributor Author

renovate bot commented Nov 28, 2022

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

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants