Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 6, 2025

This PR contains the following updates:

Package Change Age Confidence
react-konva ^18.2.10 -> ^18.2.14 age confidence

Release Notes

konvajs/react-konva (react-konva)

v18.2.14

Compare Source

v18.2.13

Compare Source

v18.2.12

Compare Source


Configuration

📅 Schedule: Branch creation - "every weekend" in timezone Europe/Berlin, 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, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added 3. to review Waiting for reviews dependencies Pull requests that update a dependency file labels Jul 6, 2025
Copy link
Contributor Author

renovate bot commented Jul 6, 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: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/react
npm error   react@"^18.3.1" from the root project
npm error   peer react@">=18.0.0" from [email protected]
npm error   node_modules/react-konva
npm error     react-konva@"^18.2.14" from the root project
npm error
npm error Could not resolve dependency:
npm error peer react@"^19.1.1" from [email protected]
npm error node_modules/react-dom
npm error   peer react-dom@">=18.0.0" from [email protected]
npm error   node_modules/react-konva
npm error     react-konva@"^18.2.14" 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 /runner/cache/others/npm/_logs/2025-09-25T18_11_25_715Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-09-25T18_11_25_715Z-debug-0.log

@renovate renovate bot requested a review from skjnldsv July 6, 2025 10:32
@renovate renovate bot added 3. to review Waiting for reviews dependencies Pull requests that update a dependency file labels Jul 6, 2025
@renovate renovate bot force-pushed the renovate/master-react-konva-18.x branch 2 times, most recently from 572399b to 787336b Compare August 13, 2025 13:40
@renovate renovate bot force-pushed the renovate/master-react-konva-18.x branch from 787336b to 93e930b Compare August 19, 2025 12:41
@renovate renovate bot force-pushed the renovate/master-react-konva-18.x branch from 93e930b to 94bd818 Compare August 31, 2025 12:26
@renovate renovate bot force-pushed the renovate/master-react-konva-18.x branch from 94bd818 to cb08707 Compare September 9, 2025 16:25
@renovate renovate bot changed the title fix(deps): update dependency react-konva to ^18.2.12 (master) fix(deps): update dependency react-konva to ^18.2.14 (master) Sep 9, 2025
@renovate renovate bot force-pushed the renovate/master-react-konva-18.x branch from cb08707 to 27185eb Compare September 25, 2025 18:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. to review Waiting for reviews dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants