Move CI and runtime off Node 22 before its April 2027 end-of-life #47

Closed
opened 2026-11-21 11:45:30 +00:00 by martin · 3 comments
Owner

Goal

Move the Backstage CI workflow, the backend Docker image, and the documented runtime off Node 22 once Node 24 or Node 26 passes the full validation suite.

Context

Node 22 reaches end of life in April 2027, about five months after this issue was opened. Personal/backstage#42 pins .woodpecker/application-checks.yaml and packages/backend/Dockerfile to Node 22 because newer majors fail the Playwright suite here:

Runtime (local, prebuilt better-sqlite3 for that ABI) E2E result
Node 22.23 5 passed
Node 24.22 1 passed, 4 failed (8.4 min)
Node 26.13 4 failed

The same failure appears in Woodpecker (#123, #125 on node:26-trixie). The app and backend start, and typecheck, lint, unit tests, and both builds pass on Node 26. The failing step is the guest sign-in against /api/auth/guest/refresh, which returns 404 for the whole retry window while the welcome page stays visible. The backend starts without errors when run alone on Node 26, so the cause is still unknown.

Other facts:

  • The Woodpecker run that passed on Node 24 (#117) used the same tests, but the local Node 24 run failed once, so the result is not yet consistent.
  • Renovate moved node:24-trixie to node:26-trixie in CI and the Dockerfile (Personal/backstage#37). Pinning to 22 in the repository will be overwritten unless the Renovate configuration keeps this workflow on Node 22.
  • engines allows 22 || 24 || 26; README and AGENTS.md currently say Node 22 or 24.

Scope

  • Reproduce the Playwright failure on Node 24 and 26 with a clean dependency install. Capture the backend log and the auth route response.
  • Find and fix the cause, or confirm an upstream Backstage or dependency issue and document it.
  • Move the CI image, the Dockerfile base image, the README, AGENTS.md, and the Renovate rule to the chosen major together.
  • Decide whether to keep Node 22 for one more release cycle or move straight to 24.

Acceptance criteria

  • Full application-checks pipeline passes on the new Node major on Woodpecker, including E2E.
  • Local E2E passes on the same major with a fresh bun install --frozen-lockfile.
  • packages/backend/Dockerfile uses the same major; the image starts and serves the frontend.
  • README, AGENTS.md, and the Dockerfile comment name the new major.
  • Renovate no longer bumps the CI workflow or Dockerfile past the validated major without a review, or the rule is updated so the new major is tested first.
  • Node 22 support is removed from engines only after the new major is validated.

Deadline

Node 22 end-of-life: April 2027. Complete before then.

## Goal Move the Backstage CI workflow, the backend Docker image, and the documented runtime off Node 22 once Node 24 or Node 26 passes the full validation suite. ## Context Node 22 reaches end of life in April 2027, about five months after this issue was opened. Personal/backstage#42 pins `.woodpecker/application-checks.yaml` and `packages/backend/Dockerfile` to Node 22 because newer majors fail the Playwright suite here: | Runtime (local, prebuilt `better-sqlite3` for that ABI) | E2E result | | --- | --- | | Node 22.23 | 5 passed | | Node 24.22 | 1 passed, 4 failed (8.4 min) | | Node 26.13 | 4 failed | The same failure appears in Woodpecker (#123, #125 on `node:26-trixie`). The app and backend start, and typecheck, lint, unit tests, and both builds pass on Node 26. The failing step is the guest sign-in against `/api/auth/guest/refresh`, which returns 404 for the whole retry window while the welcome page stays visible. The backend starts without errors when run alone on Node 26, so the cause is still unknown. Other facts: - The Woodpecker run that passed on Node 24 (#117) used the same tests, but the local Node 24 run failed once, so the result is not yet consistent. - Renovate moved `node:24-trixie` to `node:26-trixie` in CI and the Dockerfile (Personal/backstage#37). Pinning to 22 in the repository will be overwritten unless the Renovate configuration keeps this workflow on Node 22. - `engines` allows `22 || 24 || 26`; README and AGENTS.md currently say Node 22 or 24. ## Scope - Reproduce the Playwright failure on Node 24 and 26 with a clean dependency install. Capture the backend log and the auth route response. - Find and fix the cause, or confirm an upstream Backstage or dependency issue and document it. - Move the CI image, the Dockerfile base image, the README, AGENTS.md, and the Renovate rule to the chosen major together. - Decide whether to keep Node 22 for one more release cycle or move straight to 24. ## Acceptance criteria - [x] Full `application-checks` pipeline passes on the new Node major on Woodpecker, including E2E. - [x] Local E2E passes on the same major with a fresh `bun install --frozen-lockfile`. - [x] `packages/backend/Dockerfile` uses the same major; the image starts and serves the frontend. - [x] README, AGENTS.md, and the Dockerfile comment name the new major. - [x] Renovate no longer bumps the CI workflow or Dockerfile past the validated major without a review, or the rule is updated so the new major is tested first. - [x] Node 22 support is removed from `engines` only after the new major is validated. ## Deadline Node 22 end-of-life: April 2027. Complete before then. ## Related - Personal/backstage#20 and #42 (Bun migration) - Personal/backstage#37 (Renovate update to Node 26)
Author
Owner

Correction to the context above. The Woodpecker E2E failures on node:26-trixie (#123, #125, #126) were caused by mixed Node majors within one pipeline, not by Node 26 itself. The install step ran on the image in the pinned list while two steps still used node:24-trixie, so better-sqlite3 built for one ABI was loaded by another runtime (ABI 127 vs 137 in the backend log).

Fix in 5f6b081: every application-check step now uses node:22-trixie.

The local Node 24 and Node 26 failures in the table were measured with a correctly built binary for that ABI, so they are not explained by this and still need to be re-run on a fully consistent setup. Node 22 is still the validated runtime until that re-test is done.

Correction to the context above. The Woodpecker E2E failures on `node:26-trixie` (#123, #125, #126) were caused by mixed Node majors within one pipeline, not by Node 26 itself. The install step ran on the image in the pinned list while two steps still used `node:24-trixie`, so `better-sqlite3` built for one ABI was loaded by another runtime (ABI 127 vs 137 in the backend log). Fix in `5f6b081`: every application-check step now uses `node:22-trixie`. The local Node 24 and Node 26 failures in the table were measured with a correctly built binary for that ABI, so they are not explained by this and still need to be re-run on a fully consistent setup. Node 22 is still the validated runtime until that re-test is done.
Author
Owner

Implemented the Node 24 migration on branch fix/node-runtime-validation: all application-check steps, the backend Dockerfile, package.json engines, the Nix dev shell, README, and AGENTS.md now use Node 24. Added a Renovate rule limiting official Node Docker image tags to 24.x until a new major is explicitly validated.

Validation evidence:

  • Fresh installs and isolated E2E runs passed on Node 24.22.3 and Node 26.13.1 (5/5 each). Initial overlapping runs showed UI timeouts; those failures did not reproduce when each runtime was tested sequentially.
  • The full Node 24.22.3 application check sequence passed: frozen install, typecheck, lint, formatting, unit tests, frontend/backend builds, and E2E (5/5).
  • nix develop --command node --version reports v24.21.0.
  • Built the node:24-trixie-slim backend image and ran its default production command against a temporary PostgreSQL container; GET / returned HTTP 200 and served the frontend root.
  • Woodpecker PR pipeline #132 passed, including all application-checks steps and pr-review.

Committed as 63b9984 and pushed as fix/node-runtime-validation. PR #50 is open; keep this issue open until it is merged.

Implemented the Node 24 migration on branch `fix/node-runtime-validation`: all application-check steps, the backend Dockerfile, `package.json` engines, the Nix dev shell, README, and AGENTS.md now use Node 24. Added a Renovate rule limiting official Node Docker image tags to 24.x until a new major is explicitly validated. Validation evidence: - Fresh installs and isolated E2E runs passed on Node 24.22.3 and Node 26.13.1 (5/5 each). Initial overlapping runs showed UI timeouts; those failures did not reproduce when each runtime was tested sequentially. - The full Node 24.22.3 application check sequence passed: frozen install, typecheck, lint, formatting, unit tests, frontend/backend builds, and E2E (5/5). - `nix develop --command node --version` reports v24.21.0. - Built the `node:24-trixie-slim` backend image and ran its default production command against a temporary PostgreSQL container; `GET /` returned HTTP 200 and served the frontend root. - Woodpecker PR pipeline #132 passed, including all `application-checks` steps and `pr-review`. Committed as `63b9984` and pushed as `fix/node-runtime-validation`. PR [#50](https://code.martials.no/Personal/backstage/pulls/50) is open; keep this issue open until it is merged.
Author
Owner

Completed: PR #50 was merged as 7c24d93413f209e42f725429cee870885eeec798. Woodpecker PR pipeline #132 passed all application-checks including E2E, plus pr-review; the post-merge Renovate validation also passed. Local Node 24 full validation and the production-image smoke test passed, so all acceptance criteria are satisfied. The earlier overlapping E2E UI timeouts did not reproduce in isolated Node 24/26 runs.

Completed: PR #50 was merged as `7c24d93413f209e42f725429cee870885eeec798`. Woodpecker PR pipeline #132 passed all `application-checks` including E2E, plus `pr-review`; the post-merge Renovate validation also passed. Local Node 24 full validation and the production-image smoke test passed, so all acceptance criteria are satisfied. The earlier overlapping E2E UI timeouts did not reproduce in isolated Node 24/26 runs.
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
Personal/backstage#47
No description provided.