Run on Node 22 (Node.js Oct 2026 security release) #66
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
backmeupplz/banofbot!66
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?
Moves banofbot to Node 22 for the Node.js October 2026 security release (Node 16/18/20 are EOL; fixed lines are 22.23.4 / 24.22.1).
Changes
.nvmrc:v16.17.0→v22package.jsonengines.node:>=6.4→22.x. Nixpacks readsengines.nodebefore.nvmrc, and the open-ended>=6.4made it picknodejs_24, so the.nvmrcchange alone did nothing. Pinning it is what selectsnodejs_22.nixpacks.toml: pin[phases.setup] nixpkgsArchiveto a nixos-26.05 rev so the Node patch version is reproducible. This rev ships 22.23.3. It will be bumped to a rev with 22.23.4 before merge.No dependency changes.
Smoke test
nixpacks build .givesnodejs_22, yarn-1_x. The image reportsnode -v=v22.23.3(OpenSSL 3.6.5). Ranyarn startwith a throwawaymongo:7and a fake Telegram token:Modules load, Mongo connects, and the bot only fails on the fake credentials. Both
banofbotandbanofbot-silentuse this build.🤖 Generated with Claude Code