Skip to content

chore(deps): update node docker tag to v26 #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
renovate wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update node docker tag to v26 #13

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion api/Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Digest-pinned for reproducible builds (node:20-alpine index digest verified
# against the registry via `docker buildx imagetools inspect node:20-alpine`).
FROM node:20-alpine@sha256:fb4cd12c85ee03686f6af5362a0b0d56d50c58a04632e6c0fb8363f609372293
FROM node:26-alpine@sha256:e88a35be04478413b7c71c455cd9865de9b9360e1f43456be5951032d7ac1a66

@coderabbitai coderabbitai Bot Jul 20, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🩺 Stability & Availability | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Inspect the relevant files and surrounding context.
git ls-files api/Dockerfile api/package.json
printf '\n--- api/Dockerfile ---\n'
cat -n api/Dockerfile
printf '\n--- api/package.json ---\n'
cat -n api/package.json

Repository: ZenSystemAI/Zengram

Length of output: 1713

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Search for Node version policy or Docker base references across the repo.
rg -n --hidden -S 'node:2[0-9]-alpine|Node\.?js|Active LTS|Current channel|engines|docker buildx imagetools inspect' .

Repository: ZenSystemAI/Zengram

Length of output: 9175

🌐 Web query:

Official Node.js release schedule Node 26 active LTS October 2026 Docker official guidance production LTS node image

💡 Result:

As of July 20, 2026, the Node.js release schedule designates Node.js 26 as the current release, which is scheduled to transition to Active Long-Term Support (LTS) on October 28, 2026 [1][2][3]. Regarding Docker official guidance, production applications should only use LTS releases [4][5]. Therefore, you should continue to use the current Active LTS release (which is Node.js 24 as of July 2026) for production until Node.js 26 achieves its LTS status in late October 2026 [1][2][6]. Key points for your planning: - Node.js 26: Currently in the Current release phase [7][8]. It is scheduled to be promoted to Active LTS on October 28, 2026 [1][3]. - Production Guidance: The official Docker node image repository explicitly states that production applications should use LTS releases [4][5]. You can use the node:lts floating tag in your Dockerfiles to automatically track the latest Active LTS version, or pin to a specific version (e.g., node:24) for stability until you are ready to migrate to Node.js 26 after its October 2026 LTS promotion [4][5]. - Note on Future Changes: Please be aware that the Node.js project is evolving its release model; starting with Node.js 27, the release cycle will shift to an annual major release cadence where every major version transitions to LTS status after its six-month Current phase [9][6].

Citations:

Use an LTS base image here. node:26-alpine is still Current, and Docker’s production guidance is to stick to LTS releases; switch to node:24/node:lts or document the intentional Current-channel adoption. Also update the stale header comment that still mentions node:20-alpine.

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@api/Dockerfile` at line 3, Update the Dockerfile base image from the
Current-channel node:26-alpine to an LTS image such as node:24-alpine or
node:lts-alpine, preserving the digest pinning as appropriate. Also update the
stale header comment referencing node:20-alpine so it matches the selected LTS
base image.

WORKDIR /app
COPY package*.json ./
RUN npm ci --omit=dev
Expand Down
Loading