Repository navigation
chore(docker): pin Node.js base images to 24.22.1 - #1897
Conversation
Pin all Node base images to 24.22.1, the latest security release on the 24 LTS line (2026-10-20). Also moves frontend/Dockerfile off EOL Node 18 and rocketadmin-agent/Dockerfile off Node 22 onto 24. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review.
 |
| Layer / File(s) | Summary |
|---|---|
Update Docker base image references Dockerfile, Dockerfile.rocketadmin-agent, autoadmin-ws-server/Dockerfile, frontend/Dockerfile, rocketadmin-agent/Dockerfile, test/proxy-mock-api/Dockerfile |
Build and runtime stages now use Node 24.22.1 images. The frontend builder uses the public.ecr.aws/docker/library image reference. |
Priority:
Estimated code review effort: 1 (Trivial) | ~5 minutes
Change: Other
Suggested reviewers: artuomka
Merge Risk: 
f0d25
-
This change pins the Node base images to 24.22.1 across the Dockerfiles, and the frontend image now builds on a Node version its Angular tooling supports. No actionable merge-blocking risk remains. CI image builds should still be run, as the PR's test plan already says.
Pre-merge checks: 
-
Check name Status Explanation Description Check Check skipped - CodeRabbit’s high-level summary is enabled. Title check The title clearly and concisely describes the main change: pinning Docker Node.js base images to version 24.22.1. Docstring Coverage No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0… Linked Issues check Check skipped because no linked issues were found for this pull request. Out of Scope Changes check Check skipped because no linked issues were found for this pull request. Security Check The pull request only changes Node.js base-image tags. It replaces floating or older Node versions with 24.22.1in all changed Node-based Dockerfiles. It does not change application code, permission…Full details: Docstring Coverage
-
Explanation
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (6 skipped: 6 unsupported.)
Full details: Security Check
-
Explanation
The pull request only changes Node.js base-image tags. It replaces floating or older Node versions with
24.22.1in all changed Node-based Dockerfiles. It does not change application code, permissions, exposed ports, commands, dependency installation, or runtime configuration. The change reduces version drift and introduces no evidence of an OWASP-related security regression.
-
Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
A rabbit checks each image tag,
Node’s newer number fills the stack.
Slim and Alpine stand in line,
The builder hops; the runtime’s fine.
The Dockerfiles wear pins in time.
Comment @coderabbitai help to get the list of available commands.
Summary
24.22.1, the latest security release on Node 24 LTS (released 2026-10-20, per nodejs.org/dist/index.json).frontend/Dockerfile:node:18-alpine(EOL) →node:24.22.1-alpine. The rootDockerfilealready builds the frontend on Node 24.rocketadmin-agent/Dockerfile:node:22-slim→node:24.22.1-slim, matchingDockerfile.rocketadmin-agent.Dockerfile,Dockerfile.rocketadmin-agent,autoadmin-ws-server/Dockerfile,test/proxy-mock-api/Dockerfile: floatingnode:24-*→node:24.22.1-*.These are exact pins, so future patch releases won't be picked up automatically. Bump them manually or with Dependabot/Renovate.
Test plan
🤖 Generated with Claude Code
Summary by CodeRabbit