Run on Node 22 (Node.js Oct 2026 security release) #11
No reviewers
Labels
No labels
bug
dependencies
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
backmeupplz/voicy-payments!11
Loading…
Reference in a new issue
No description provided.
Delete branch "node-22-security"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
Node.js shipped a security release on 2026-10-21. Node 16/18/20 are EOL and get no fix; this service runs Node 18.20.5. Fixed lines are 22.23.4 / 24.22.1.
What
.nvmrc:v17.0.1->v22(Nixpacks resolves this tonodejs_22; confirmed withnixpacks plan .)nixpacks.toml: pin[phases.setup] nixpkgsArchiveto nixos-26.05 revcd4ea8d5…, which has nodejs 22.23.3. It will be swapped for a rev with 22.23.4 once that reaches the channel, before merging.enginesfield.Smoke test (local
nixpacks build, Node v22.23.3, OpenSSL 3.6.5)node ./bin/wwwwith fake credentials against amongo:4.4container:Server is up and running!,Listening on port 3001,New stats were generated!GET /statsfornikita-> 200,GET /statsforashmanov-> 200StripeAuthenticationError; TelegramgetMewith a fake token -> 401. So TLS and the HTTP clients work, and only the credentials are rejected.DEP0044 util.isArray, from old deps). It still works on 22, but these APIs are removed in Node 23+.Note: mongoose 4 / mongodb-core 2 cannot talk to MongoDB >= 5.1 (
OP_QUERYremoved). This is unrelated to Node and the same as before; production Mongo must already be older.Not deployed, not merged.
🤖 Generated with Claude Code