Skip to content

chore(deps): update dependency @types/node to ^22.9.0#1238

Closed
renovate[bot] wants to merge 1 commit intomainfrom
renovate/node-22.x
Closed

chore(deps): update dependency @types/node to ^22.9.0#1238
renovate[bot] wants to merge 1 commit intomainfrom
renovate/node-22.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Jul 5, 2025

This PR contains the following updates:

Package Change Age Confidence
@types/node (source) ^24.3.0 -> ^22.9.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 force-pushed the renovate/node-22.x branch 2 times, most recently from 8bd7292 to 6625ce3 Compare July 8, 2025 14:22
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Jul 12, 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: node/pnpm-lock.yaml
 ERROR  Failed to switch pnpm to v10.13.1. Looks like pnpm CLI is missing at "/home/ubuntu/.local/share/pnpm/.tools/pnpm/10.13.1/bin" or is incorrect
spawnSync /home/ubuntu/.local/share/pnpm/.tools/pnpm/10.13.1/bin/pnpm ENOENT

@renovate renovate Bot force-pushed the renovate/node-22.x branch 6 times, most recently from 8e99754 to 3cd6dfa Compare July 15, 2025 22:43
@renovate renovate Bot changed the title chore(deps): update dependency node to v22.17.0 chore(deps): update dependency node to v22.17.1 Jul 15, 2025
@renovate renovate Bot force-pushed the renovate/node-22.x branch 3 times, most recently from 487d18a to 2b5428b Compare July 31, 2025 02:53
@Nickersoft Nickersoft force-pushed the renovate/node-22.x branch from 2b5428b to fc407b8 Compare July 31, 2025 02:54
@renovate renovate Bot force-pushed the renovate/node-22.x branch 2 times, most recently from 0491ada to ed028e0 Compare August 6, 2025 15:08
@renovate renovate Bot changed the title chore(deps): update dependency node to v22.17.1 chore(deps): update dependency node to v22.18.0 Aug 6, 2025
@renovate renovate Bot force-pushed the renovate/node-22.x branch from ed028e0 to f1c7f36 Compare August 6, 2025 15:14
@renovate renovate Bot force-pushed the renovate/node-22.x branch 3 times, most recently from 1b8ab1e to cf6358f Compare August 15, 2025 21:21
@renovate renovate Bot changed the title chore(deps): update dependency node to v22.18.0 chore(deps): update dependency @types/node to ^22.9.0 Aug 16, 2025
@renovate renovate Bot force-pushed the renovate/node-22.x branch from cf6358f to e5924c1 Compare August 16, 2025 02:42
@Nickersoft Nickersoft closed this Aug 16, 2025
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Aug 16, 2025

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (^22.9.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

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/node-22.x branch August 16, 2025 02:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant