chore: update Node.js to v22 LTS (22.23.1) - #743
Merged
Conversation
renovate
Bot
requested review from
JamesRobert20,
edelauna,
hannesrudolph,
navedmerchant and
taltas
as code owners
June 27, 2026 15:50
renovate
Bot
force-pushed
the
renovate/node-24.x
branch
from
June 27, 2026 16:09
5a584b5 to
755c0ca
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
renovate
Bot
force-pushed
the
renovate/node-24.x
branch
3 times, most recently
from
July 1, 2026 00:35
9ef6744 to
cd12bea
Compare
github-actions
Bot
added
has-conflicts
github-actions
Bot
added
has-conflicts
github-actions
Bot
added
the
has-conflicts
renovate
Bot
force-pushed
the
renovate/node-24.x
branch
from
July 18, 2026 23:33
cd12bea to
bd3aa07
Compare
github-actions
Bot
removed
the
has-conflicts
renovate
Bot
force-pushed
the
renovate/node-24.x
branch
3 times, most recently
from
July 24, 2026 14:25
5fa9256 to
04f17bf
Compare
edelauna
force-pushed
the
renovate/node-24.x
branch
from
July 25, 2026 17:52
04f17bf to
fa4b73b
Compare
edelauna
changed the title
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
edelauna
approved these changes
Jul 25, 2026
edelauna
left a comment
edelauna
left a comment
Contributor
There was a problem hiding this comment.
bumping to v22 since v24 has issues with windows
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Renovate proposed bumping Node from 20 → 24, but Node 24 triggers a deterministic libuv assertion abort on the Windows CI runner (`fs-event.c:72`, Windows Server 2025) causing `platform-unit-test (windows-latest)` to fail on every run. This is an upstream Node/libuv regression with no fix available yet.
This PR redirects the bump to Node 22 LTS (supported until 2027-04-30), which is stable on Windows.
Changes
Why not Node 24?
`nodejs/node#56645` and related issues document a class of libuv assertion failures on Windows that affect Node 23/24. The specific crash here is:
```
Assertion failed: !_wcsnicmp(filename, dir, dirlen), file src\win\fs-event.c, line 72
```
It fires deterministically during `zoo-code:test:coverage` whenever the fs watcher is active. Linux CI is unaffected. A follow-up PR can re-attempt the Node 24 bump once an upstream patch lands.