Skip to content

Replace dependency @tsconfig/node18 with @tsconfig/node20#149

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/tsconfig-node18-replacement
Open

Replace dependency @tsconfig/node18 with @tsconfig/node20#149
renovate[bot] wants to merge 1 commit intomainfrom
renovate/tsconfig-node18-replacement

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate bot commented Mar 5, 2026

This PR contains the following updates:

Package Type Update Change
@tsconfig/node18 (source) → @tsconfig/node20 replacement 1820
@tsconfig/node18 (source) → @tsconfig/node20 devDependencies replacement ^18.2.4^20.1.0

This is a special PR that replaces @tsconfig/node18 with the community suggested minimal stable replacement version.


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 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
Copy Markdown
Author

renovate bot commented Mar 5, 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: pnpm-lock.yaml
(node:904) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)

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