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 dependency react-scripts to v5 #22

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 1, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
react-scripts 4.0.3 -> 5.0.1 age adoption passing confidence

Release Notes

facebook/create-react-app

v5.0.1

Compare Source

Inside any created project that has not been ejected, run:

npm install --save --save-exact [email protected]

or

yarn add --exact [email protected]
🐛 Bug Fix
💅 Enhancement
📝 Documentation
🏠 Internal
Committers: 11

5.0.0 (2021-12-14)

Create React App 5.0 is a major release with several new features and the latest version of all major dependencies.

Thanks to all the maintainers and contributors who worked so hard on this release! 🙌

v5.0.0

Compare Source

Inside any created project that has not been ejected, run:

npm install --save --save-exact [email protected]

or

yarn add --exact [email protected]
🐛 Bug Fix
💅 Enhancement
📝 Documentation
🏠 Internal
Committers: 11

5.0.0 (2021-12-14)

Create React App 5.0 is a major release with several new features and the latest version of all major dependencies.

Thanks to all the maintainers and contributors who worked so hard on this release! 🙌


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 this update again.


  • If you want to rebase/retry this PR, click this checkbox.

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

@renovate
Copy link
Contributor Author

renovate bot commented Feb 1, 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 notice 
npm notice New minor version of npm available! 8.5.0 -> 8.6.0
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v8.6.0>
npm notice Run `npm install -g [email protected]` to update!
npm notice 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @craco/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react-scripts
npm ERR!   react-scripts@"5.0.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react-scripts@"^4.0.0" from @craco/[email protected]
npm ERR! node_modules/@craco/craco
npm ERR!   @craco/craco@"6.4.3" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react-scripts
npm ERR!   peer react-scripts@"^4.0.0" from @craco/[email protected]
npm ERR!   node_modules/@craco/craco
npm ERR!     @craco/craco@"6.4.3" 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-04-12T19_52_07_229Z-debug-0.log

@renovate renovate bot force-pushed the renovate/react-scripts-5.x branch from 1b8313e to 677fccd Compare February 1, 2022 21:12
@netlify
Copy link

netlify bot commented Feb 1, 2022

❌ Deploy Preview for zen-wright-08976a failed.

🔨 Explore the source changes: 984cb07

🔍 Inspect the deploy log: https://app.netlify.com/sites/zen-wright-08976a/deploys/623233dac3119c00097a94b6

@renovate renovate bot force-pushed the renovate/react-scripts-5.x branch 5 times, most recently from d3f775b to c5986ef Compare February 3, 2022 04:31
@renovate renovate bot force-pushed the renovate/react-scripts-5.x branch 3 times, most recently from 11cb855 to 66e13c1 Compare February 16, 2022 03:51
@renovate renovate bot force-pushed the renovate/react-scripts-5.x branch 2 times, most recently from d948998 to 76000d3 Compare February 18, 2022 05:39
@renovate renovate bot force-pushed the renovate/react-scripts-5.x branch 5 times, most recently from 9bfdb4f to 51ff96d Compare March 1, 2022 19:25
@renovate renovate bot force-pushed the renovate/react-scripts-5.x branch 3 times, most recently from cca1c66 to feb1406 Compare March 10, 2022 11:42
@renovate renovate bot force-pushed the renovate/react-scripts-5.x branch 2 times, most recently from bdebf0b to 984cb07 Compare March 16, 2022 19:00
@renovate
Copy link
Contributor Author

renovate bot commented Aug 21, 2022

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 5.x releases. But if you manually upgrade to 5.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/react-scripts-5.x branch August 21, 2022 06:09
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