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

chore(deps): update react monorepo #31

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 16, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/react (source) 18.2.77 -> 18.3.9 age adoption passing confidence
@types/react-dom (source) 18.2.25 -> 18.3.0 age adoption passing confidence
react (source) 18.2.0 -> 18.3.1 age adoption passing confidence
react-dom (source) 18.2.0 -> 18.3.1 age adoption passing confidence

Release Notes

facebook/react (react)

v18.3.1

Compare Source

v18.3.0

Compare Source

facebook/react (react-dom)

v18.3.1

Compare Source

v18.3.0

Compare Source


Configuration

📅 Schedule: Branch creation - "before 6am,every weekend" in timezone Europe/Oslo, 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.

Copy link
Contributor Author

renovate bot commented Apr 16, 2024

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

Copy link
Contributor Author

renovate bot commented Apr 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: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: @cloudflare/[email protected]
npm ERR! node_modules/@cloudflare/workers-types
npm ERR!   dev @cloudflare/workers-types@"3.19.0" from the root project
npm ERR!   peer @cloudflare/workers-types@"^2.0.0 || ^3.0.0" from @remix-run/[email protected]
npm ERR!   node_modules/@remix-run/cloudflare
npm ERR!     @remix-run/cloudflare@"1.11.1" from the root project
npm ERR!     @remix-run/cloudflare@"1.11.1" from @remix-run/[email protected]
npm ERR!     node_modules/@remix-run/cloudflare-pages
npm ERR!       @remix-run/cloudflare-pages@"1.11.1" from the root project
npm ERR!   1 more (@remix-run/cloudflare-pages)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional @cloudflare/workers-types@"^4.20240405.0" from [email protected]
npm ERR! node_modules/wrangler
npm ERR!   dev wrangler@"3.51.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @cloudflare/[email protected]
npm ERR! node_modules/@cloudflare/workers-types
npm ERR!   peerOptional @cloudflare/workers-types@"^4.20240405.0" from [email protected]
npm ERR!   node_modules/wrangler
npm ERR!     dev wrangler@"3.51.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/2024-04-29T21_52_55_758Z-debug-0.log

@renovate renovate bot force-pushed the renovate/react-monorepo branch from b410194 to 1fc4c61 Compare April 18, 2024 14:15
Copy link

cloudflare-workers-and-pages bot commented Apr 18, 2024

Deploying capracon-2023 with  Cloudflare Pages  Cloudflare Pages

Latest commit: 691b2c3
Status: ✅  Deploy successful!
Preview URL: https://e3a1e77b.capracon-2023.pages.dev
Branch Preview URL: https://renovate-react-monorepo.capracon-2023.pages.dev

View logs

@renovate renovate bot force-pushed the renovate/react-monorepo branch 2 times, most recently from 42b277f to 3d9ba68 Compare April 18, 2024 22:18
@renovate renovate bot changed the title chore(deps): update dependency @types/react to v18.2.78 chore(deps): update dependency @types/react to v18.2.79 Apr 18, 2024
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 3d9ba68 to 3a2416d Compare April 28, 2024 18:36
@renovate renovate bot changed the title chore(deps): update dependency @types/react to v18.2.79 chore(deps): update react monorepo Apr 28, 2024
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 3a2416d to 5becafb Compare April 28, 2024 22:12
@renovate renovate bot changed the title chore(deps): update react monorepo chore(deps): update react monorepo to v18.3.0 Apr 28, 2024
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 5becafb to 8008552 Compare April 29, 2024 20:27
@renovate renovate bot changed the title chore(deps): update react monorepo to v18.3.0 chore(deps): update react monorepo Apr 29, 2024
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 8008552 to caca3fe Compare April 29, 2024 21:53
@renovate renovate bot force-pushed the renovate/react-monorepo branch from caca3fe to bc6b015 Compare May 14, 2024 10:47
Copy link
Contributor Author

renovate bot commented May 14, 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: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: @cloudflare/[email protected]
npm ERR! node_modules/@cloudflare/workers-types
npm ERR!   dev @cloudflare/workers-types@"3.19.0" from the root project
npm ERR!   peer @cloudflare/workers-types@"^2.0.0 || ^3.0.0" from @remix-run/[email protected]
npm ERR!   node_modules/@remix-run/cloudflare
npm ERR!     @remix-run/cloudflare@"1.11.1" from the root project
npm ERR!     @remix-run/cloudflare@"1.11.1" from @remix-run/[email protected]
npm ERR!     node_modules/@remix-run/cloudflare-pages
npm ERR!       @remix-run/cloudflare-pages@"1.11.1" from the root project
npm ERR!   1 more (@remix-run/cloudflare-pages)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional @cloudflare/workers-types@"^4.20240405.0" from [email protected]
npm ERR! node_modules/wrangler
npm ERR!   dev wrangler@"3.51.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @cloudflare/[email protected]
npm ERR! node_modules/@cloudflare/workers-types
npm ERR!   peerOptional @cloudflare/workers-types@"^4.20240405.0" from [email protected]
npm ERR!   node_modules/wrangler
npm ERR!     dev wrangler@"3.51.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/2024-09-27T15_17_32_750Z-debug-0.log

@renovate renovate bot force-pushed the renovate/react-monorepo branch from bc6b015 to b651d46 Compare May 26, 2024 20:16
@renovate renovate bot force-pushed the renovate/react-monorepo branch 3 times, most recently from f4f57d7 to 6458fb8 Compare September 22, 2024 20:04
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