Skip to content
This repository was archived by the owner on Sep 11, 2025. It is now read-only.

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 8, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/react (source) ^18.3.13 -> ^19.0.0 age adoption passing confidence
@types/react-dom (source) ^18.2.0 -> ^19.0.0 age adoption passing confidence
react (source) ^18.2.0 -> ^19.0.0 age adoption passing confidence
react-dom (source) ^18.2.0 -> ^19.0.0 age adoption passing confidence

Release Notes

facebook/react (react)

v19.0.0

Compare Source

facebook/react (react-dom)

v19.0.0

Compare Source


Configuration

📅 Schedule: Branch creation - "on Wednesday" (UTC), 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
Copy link
Contributor Author

renovate bot commented Jan 8, 2025

⚠️ 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: runtime/explorer/content/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @hypermode/[email protected]
npm error Found: [email protected]
npm error node_modules/react
npm error   react@"^19.0.0" from the root project
npm error   peer react@">=16.8.0" from @uiw/[email protected]
npm error   node_modules/@uiw/react-codemirror
npm error     @uiw/react-codemirror@"^4.23.6" from @hypermode/[email protected]
npm error     node_modules/@hypermode/react-api-explorer
npm error       @hypermode/react-api-explorer@"^1.0.0-alpha.16" from the root project
npm error   2 more (zustand, react-dom)
npm error
npm error Could not resolve dependency:
npm error peer react@"^18.2.0" from @hypermode/[email protected]
npm error node_modules/@hypermode/react-api-explorer
npm error   @hypermode/react-api-explorer@"^1.0.0-alpha.16" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/react
npm error   peer react@"^18.2.0" from @hypermode/[email protected]
npm error   node_modules/@hypermode/react-api-explorer
npm error     @hypermode/react-api-explorer@"^1.0.0-alpha.16" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2025-01-08T01_40_08_511Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-01-08T01_40_08_511Z-debug-0.log

@renovate renovate bot requested a review from a team January 8, 2025 01:40
@mattjohnsonpint mattjohnsonpint added the do-not-merge DO NOT MERGE label Jan 8, 2025
@mattjohnsonpint
Copy link
Contributor

The @hypermode/react-api-explorer component will need to be updated before this can be merged.

@kristencheung - please take a look. Thanks.

@kristencheung
Copy link
Contributor

closing in favor of #700

@renovate
Copy link
Contributor Author

renovate bot commented Jan 10, 2025

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 19.x releases. But if you manually upgrade to 19.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/major-react-monorepo branch January 10, 2025 21:09
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

do-not-merge DO NOT MERGE

Development

Successfully merging this pull request may close these issues.

3 participants