Run on Node 22 (Node.js Oct 2026 security release) #6

Merged
backmeupplz merged 2 commits from node-22-security into main 2026-10-21 17:05:53 +00:00
backmeupplz commented 2026-10-21 14:54:44 +00:00 (Migrated from github.com)

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 gives engines priority over .nvmrc, and >=20 was resolving to nodejs_24.
  • .nvmrc: new, v22.
  • nixpacks.toml: new, pins only [phases.setup] nixpkgsArchive (nixos-26.05 rev with nodejs_22). We'll swap in the 22.23.4 rev before merge.
  • Dockerfile: unchanged. It already uses node:22-alpine, and Easypanel builds with Nixpacks anyway.

nixpacks plan . before and after: the only change in setup is nodejs_24 → nodejs_22 plus the archive rev. npm-9_x, the overlay, npm ci and the npm run start start command are all unchanged.

Smoke test (local nixpacks build)

node v22.23.3, npm 10.9.9, OpenSSL 3.6.5
node --test: 7 pass, 0 fail; npm run check: ok
no env:     Error: TELEGRAM_BOT_TOKEN is required
dummy env:  Watching Veydrift from block 52902547 on Base mainnet
            Polling failed; ... RpcRequestError ... request limit reached (public mainnet.base.org rate limit)

Modules load, viem's HTTPS reaches Base, and nothing failed on ABI or OpenSSL.

Not merged or deployed.

🤖 Generated with Claude Code

## 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 gives `engines` priority over `.nvmrc`, and `>=20` was resolving to `nodejs_24`. - `.nvmrc`: new, `v22`. - `nixpacks.toml`: new, pins only `[phases.setup] nixpkgsArchive` (nixos-26.05 rev with `nodejs_22`). We'll swap in the 22.23.4 rev before merge. - `Dockerfile`: unchanged. It already uses `node:22-alpine`, and Easypanel builds with Nixpacks anyway. `nixpacks plan .` before and after: the only change in setup is `nodejs_24` → `nodejs_22` plus the archive rev. `npm-9_x`, the overlay, `npm ci` and the `npm run start` start command are all unchanged. ## Smoke test (local `nixpacks build`) ``` node v22.23.3, npm 10.9.9, OpenSSL 3.6.5 node --test: 7 pass, 0 fail; npm run check: ok no env: Error: TELEGRAM_BOT_TOKEN is required dummy env: Watching Veydrift from block 52902547 on Base mainnet Polling failed; ... RpcRequestError ... request limit reached (public mainnet.base.org rate limit) ``` Modules load, viem's HTTPS reaches Base, and nothing failed on ABI or OpenSSL. Not merged or deployed. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Borodutch/veydrift-solar-satellite-bot!6
No description provided.