Repository navigation
chore(deps): update dependency nodejs/node to v24.22.2 - #763
Conversation
|
Note No rendered changes. konflate 0.6.6 · rendered |
shrinedogg
left a comment
There was a problem hiding this comment.
Verified patch bump of the mise node pin (markdownlint-cli2 host) from 24.22.1 to 24.22.2.
Verified locally:
- Fetched the PR head (98c8e39) and diffed it against GitHub main: exactly one commit, one file. mise.toml line 16 changes node from "24.22.1" to "24.22.2". The commit title matches the diff.
- Upstream artifact exists: nodejs/node release tag v24.22.2 ("2026-10-28, Version 24.22.2 'Krypton' (LTS)"), published 2026-10-28.
- Version compatibility: the Renovate 44.x CLI pinned in CI declares engines node ^24.11.0, and the renovate.json5 cap merged on main (allowedVersions "<25") both allow 24.22.2.
- CI at head 98c8e39: 12 of 13 check runs pass, including Markdown lint (the job that installs and uses the mise node pin via markdownlint-cli2), Docker image build, and Renovate airgap digest pinning.
- The one red check, "AWS arm (boot scope)", is a runner-side flake, not a PR effect: the CAPA controller-manager timed out at 600s and the pod shows ImagePullBackOff. The same failure happened within 15 minutes (14:28-14:43 UTC, 2026-11-09) on 3 unrelated PRs (renovate/nodejs-node-26.x, renovate/github-actions, renovate/cluster-api), and the cluster-api run log shows the same capa ImagePullBackOff. This PR's single change (a node patch in the mise pin) is not consumed by the AWS arm job. A rerun should clear it.
Release notes: v24.22.1 -> v24.22.2 (checked the upstream release): 5 V8 backports/cherry-picks (nodejs/node#66249, nodejs/node#65764 x3, nodejs/node#66241) and one stream fix, "keep async context of parked writes" (nodejs/node#66907). No breaking changes, no documented known bugs.
Suggestion: merge this together with the companion PR #762 (setup-node pin to 24.22.2 in .github/workflows/validate.yml). The comment on the changed line requires the two node pins to stay aligned, and the renovate.json5 cap rule tracks the two pins as separate PRs, so landing the pair together keeps them aligned.
VERDICT: APPROVE
| # Markdown linting (#243): node hosts markdownlint-cli2. Keep the node pin | ||
| # aligned with the setup-node pin in .github/workflows/validate.yml. | ||
| node = "24.22.1" | ||
| node = "24.22.2" |
There was a problem hiding this comment.
Suggestion: land this with companion PR #762 (setup-node 24.22.2 in .github/workflows/validate.yml) so the two node pins stay aligned, as the comment on this line requires. The renovate.json5 cap rule tracks the two pins as separate PRs, so alignment depends on merging the pair.
This PR contains the following updates:
24.22.1→24.22.2Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
nodejs/node
v24.22.2: 2026-10-28, Version 24.22.2 'Krypton' (LTS), @aduh95Compare Source
Commits
f8bdcd54ed] - deps: V8: backport786c1c2(Eliau Elkouby) #662493b93fd6b2b] - deps: V8: backport1a00890(Jakob Linke) #657645aaf62faaa] - deps: V8: backportc9c0abf(Jakob Linke) #657643b8eb1a920] - deps: V8: backportebd1578(Marja Hölttä) #65764ab70b5d681] - deps: V8: cherry-pick853553f(Victor Gomes) #6624117ec999f24] - stream: keep async context of parked writes (Matteo Collina) #66907Configuration
📅 Schedule: (in timezone Europe/Helsinki)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.