Skip to content

Update dependency @types/node to v24#28

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/node-24.x
Open

Update dependency @types/node to v24#28
renovate[bot] wants to merge 1 commit intomainfrom
renovate/node-24.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 19, 2025

This PR contains the following updates:

Package Change Age Confidence
@types/node (source) ^16.7.13^24.0.0 age confidence

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 is behind base branch, 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 the renovate label Nov 19, 2025
@renovate renovate bot force-pushed the renovate/node-24.x branch 2 times, most recently from cb5046c to bf3270b Compare December 17, 2025 11:49
@renovate renovate bot force-pushed the renovate/node-24.x branch 2 times, most recently from 31d972b to dd73d67 Compare January 16, 2026 23:30
@renovate renovate bot force-pushed the renovate/node-24.x branch 2 times, most recently from e93d0de to 98a9241 Compare February 4, 2026 20:26
@renovate
Copy link
Contributor Author

renovate bot commented Feb 4, 2026

⚠️ 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 warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @testing-library/react@13.4.0
npm error Found: react@19.2.4
npm error node_modules/react
npm error   react@"^19.2.4" from the root project
npm error   peer react@">=16" from @descope/react-sdk@2.26.2
npm error   node_modules/@descope/react-sdk
npm error     @descope/react-sdk@"^2.26.2" from the root project
npm error   3 more (@reduxjs/toolkit, react-dom, react-scripts)
npm error
npm error Could not resolve dependency:
npm error peer react@"^18.0.0" from @testing-library/react@13.4.0
npm error node_modules/@testing-library/react
npm error   @testing-library/react@"^13.0.0" from the root project
npm error
npm error Conflicting peer dependency: react@18.3.1
npm error node_modules/react
npm error   peer react@"^18.0.0" from @testing-library/react@13.4.0
npm error   node_modules/@testing-library/react
npm error     @testing-library/react@"^13.0.0" 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/2026-02-17T18_57_19_121Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-02-17T18_57_19_121Z-debug-0.log

@renovate renovate bot force-pushed the renovate/node-24.x branch 3 times, most recently from 3586379 to 353cdb4 Compare February 8, 2026 14:52
@renovate renovate bot force-pushed the renovate/node-24.x branch from 353cdb4 to b33a11a Compare February 11, 2026 03:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants

Comments