Run on Node 22 (Node.js Oct 2026 security release) #6
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
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
Borodutch/veydrift-solar-satellite-bot!6
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?
What
Moves the bot from Node 24 to Node 22 for the Node.js Oct 21 2026 security release. Node 24's patched build won't reach nixpkgs for a while; the 22.x fix (22.23.4) lands first.
package.json/package-lock.json:engines.node>=20→22.x. Nixpacks givesenginespriority over.nvmrc, and>=20was resolving tonodejs_24..nvmrc: new,v22.nixpacks.toml: new, pins only[phases.setup] nixpkgsArchive(nixos-26.05 rev withnodejs_22). We'll swap in the 22.23.4 rev before merge.Dockerfile: unchanged. It already usesnode:22-alpine, and Easypanel builds with Nixpacks anyway.nixpacks plan .before and after: the only change in setup isnodejs_24→nodejs_22plus the archive rev.npm-9_x, the overlay,npm ciand thenpm run startstart command are all unchanged.Smoke test (local
nixpacks build)Modules load, viem's HTTPS reaches Base, and nothing failed on ABI or OpenSSL.
Not merged or deployed.
🤖 Generated with Claude Code