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

Update react monorepo to v16.14.0 #60

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Feb 26, 2020

This PR contains the following updates:

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

Release Notes

facebook/react (react)

v16.14.0

Compare Source

React

v16.13.1

Compare Source

React DOM
  • Fix bug in legacy mode Suspense where effect clean-up functions are not fired. This only affects users who use Suspense for data fetching in legacy mode, which is not technically supported. (@​acdlite in #​18238)
  • Revert warning for cross-component updates that happen inside class render lifecycles (componentWillReceiveProps, shouldComponentUpdate, and so on). (@​gaearon in #​18330)

v16.13.0

Compare Source

React
React DOM
Concurrent Mode (Experimental)

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.

🔕 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/react-monorepo branch from 00d031e to 07fce23 Compare March 19, 2020 20:19
@renovate renovate bot changed the title Update react monorepo to v16.13.0 Update react monorepo to v16.13.1 Mar 19, 2020
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 07fce23 to 4d50f25 Compare March 26, 2020 17:36
@renovate renovate bot changed the title Update react monorepo to v16.13.1 Update react monorepo Mar 26, 2020
@renovate renovate bot force-pushed the renovate/react-monorepo branch 2 times, most recently from 0601dea to f871f74 Compare April 8, 2020 17:12
@renovate renovate bot force-pushed the renovate/react-monorepo branch 5 times, most recently from 361715e to 8247723 Compare July 15, 2020 13:47
@renovate renovate bot force-pushed the renovate/react-monorepo branch 2 times, most recently from d3e1704 to e23358a Compare July 23, 2020 16:41
@renovate renovate bot force-pushed the renovate/react-monorepo branch from e23358a to d2895fd Compare July 31, 2020 13:26
@renovate renovate bot force-pushed the renovate/react-monorepo branch from d2895fd to 762b600 Compare September 29, 2020 15:41
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 762b600 to 08f4125 Compare October 28, 2020 05:58
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 08f4125 to 7ab571f Compare December 9, 2020 14:00
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 7ab571f to 23d92d8 Compare April 26, 2021 13:42
@renovate
Copy link
Author

renovate bot commented Apr 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! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"16.14.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"17.0.1" from [email protected]
npm ERR! node_modules/react-native
npm ERR!   react-native@"0.64.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/2021-04-26T13_42_41_454Z-debug.log

@renovate renovate bot force-pushed the renovate/react-monorepo branch from 23d92d8 to c23c146 Compare May 9, 2021 22:15
@renovate
Copy link
Author

renovate bot commented May 9, 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! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"16.14.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"17.0.1" from [email protected]
npm ERR! node_modules/react-native
npm ERR!   react-native@"0.64.1" 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-05-09T22_14_45_284Z-debug.log

@renovate renovate bot force-pushed the renovate/react-monorepo branch from c23c146 to 389ef59 Compare June 6, 2021 20:59
@renovate renovate bot changed the title Update react monorepo Update react monorepo to v16.14.0 Oct 20, 2021
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 389ef59 to 26144a8 Compare September 25, 2022 21:33
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 26144a8 to 2a6d494 Compare November 20, 2022 12:52
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