MISMATCH: Dockerfile uses Node 20, CI uses Node 22 — inconsistent runtime #7

Closed
opened 2026-05-09 00:27:27 +00:00 by Mark · 0 comments
Owner

Description

The production Dockerfile and the CI pipeline use different Node.js versions, which could lead to differences in behavior between CI-tested code and deployed code.

The Issue

  • Dockerfile (line 1): FROM node:20-alpine — production runs on Node 20
  • .forgejo/workflows/ci.yml (lines 17, 33, 49): node-version: 22 — all CI jobs use Node 22

Impact

  • Code that passes tests on Node 22 might behave differently or break on Node 20 in production
  • For example, Node 22 has different JavaScript features, ICU data, and TLS behavior than Node 20
  • Dependencies might resolve differently or have different compatibility

Fix

Match the versions. Either:

  1. Update the Dockerfile to use node:22-alpine
  2. Or update the CI to use node-version: 20

Since the Dockerfile runs npm ci --legacy-peer-deps and the app was developed with Node 24.x locally (per build-output.log), aligning to the newer version is recommended.

## Description The production Dockerfile and the CI pipeline use different Node.js versions, which could lead to differences in behavior between CI-tested code and deployed code. ## The Issue - `Dockerfile` (line 1): `FROM node:20-alpine` — production runs on Node 20 - `.forgejo/workflows/ci.yml` (lines 17, 33, 49): `node-version: 22` — all CI jobs use Node 22 ## Impact - Code that passes tests on Node 22 might behave differently or break on Node 20 in production - For example, Node 22 has different JavaScript features, ICU data, and TLS behavior than Node 20 - Dependencies might resolve differently or have different compatibility ## Fix Match the versions. Either: 1. Update the Dockerfile to use `node:22-alpine` 2. Or update the CI to use `node-version: 20` Since the Dockerfile runs `npm ci --legacy-peer-deps` and the app was developed with Node 24.x locally (per build-output.log), aligning to the newer version is recommended.
Mark closed this issue 2026-05-09 16:12:19 +00:00
Sign in to join this conversation.
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
AuWoMe/planish#7
No description provided.