Node 22 base image upgradeNode 22 base image upgrade
You
Bump the Node base image to 22 across all services and fix breakage.
Assistant
I opened a PR that bumps the Node base image and fixes the one breaking change.
| Service | Old image | New image | Result |
|---|---|---|---|
| api | node:20.11 | node:22.9 | tests pass |
| worker | node:20.11 | node:22.9 | tests pass |
| realtime | node:20.11 | node:22.9 | 1 fix needed |
The realtime service relied on the removed --experimental-fetch flag; I dropped it since fetch is stable now.
You
Where exactly was the experimental fetch flag used?
Assistant
The removed flag was only set in services/realtime/Dockerfile, as CMD ["node", "--experimental-fetch", "dist/main.js"]. Node 22 ships fetch enabled by default, so the process now starts with no flags.
You
Anything else I should know before merging?
Assistant
Two things to check before merging:
- The CI runners cache the old image layer; the first build will be about 3 minutes slower.
- Native modules are rebuilt, and
sharppulled a new prebuilt binary.
You
Run the full suite once more on the branch.
Assistant
Done. I re-ran the full suite on the PR branch and every service passes: api, worker and realtime.