Skip to content

Update dependency @types/node to v24.13.6 - #2793

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/node-24.13.x
Open

renovate[bot] wants to merge 1 commit into
masterfrom
renovate/node-24.13.x

Conversation

@renovate

@renovate renovate Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@types/node (source) 24.13.324.13.6 age confidence

Configuration

📅 Schedule: (in timezone Asia/Shanghai)

  • Branch creation
    • "after 2am and before 8am on friday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

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-approve[bot]
renovate-approve Bot previously approved these changes Sep 10, 2026
@renovate

renovate Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ 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. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: eesast-web@2024.0.0
npm error Found: graphql@17.0.2
npm error node_modules/graphql
npm error   graphql@"17.0.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer graphql@"^15.0.0 || ^16.0.0" from @apollo/client@3.14.1
npm error node_modules/@apollo/client
npm error   @apollo/client@"3.14.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps 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-09-19T02_01_03_715Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-19T02_01_03_715Z-debug-0.log

@mergify mergify Bot added the dependencies Pull requests that update a dependency file label Sep 10, 2026
@mergify

mergify Bot commented Sep 10, 2026

Copy link
Copy Markdown

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

  • Queue this pull request

renovate-approve[bot]
renovate-approve Bot previously approved these changes Sep 15, 2026
@renovate renovate Bot changed the title Update dependency @types/node to v24.13.4 Update dependency @types/node to v24.13.5 Sep 15, 2026
@renovate
renovate Bot force-pushed the renovate/node-24.13.x branch from 57e49d4 to b0c5aa7 Compare September 16, 2026 15:29
@renovate
renovate Bot force-pushed the renovate/node-24.13.x branch from b0c5aa7 to 07f7287 Compare September 19, 2026 02:01
@renovate renovate Bot changed the title Update dependency @types/node to v24.13.5 Update dependency @types/node to v24.13.6 Sep 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants