chore(deps): update node docker tag to v26#13
Conversation
📝 WalkthroughWalkthroughThe API Dockerfile base image is upgraded from Node.js 20 Alpine to Node.js 26 Alpine, including its pinned SHA-256 digest. All other Dockerfile instructions remain unchanged. ChangesAPI container build
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with 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.
Inline comments:
In `@api/Dockerfile`:
- 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.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| # 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 |
There was a problem hiding this comment.
🩺 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.jsonRepository: 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:
- 1: https://github.com/nodejs/release/
- 2: https://github.com/nodejs/Release/blob/main/README.md
- 3: https://github.com/nodejs/release
- 4: https://github.com/nodejs/docker-node/
- 5: https://github.com/nodejs/docker-node/blob/master/README.md
- 6: https://nodejs.org/en/about/previous-releases
- 7: https://nodejs.org/en/blog/release/v26.0.0
- 8: https://github.com/nodejs/node/releases/tag/v26.0.0
- 9: https://nodejs.org/en/blog/announcements/evolving-the-nodejs-release-schedule
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.
7c7c29f to
cd6b214
Compare
This PR contains the following updates:
20-alpine→26-alpineRelease Notes
nodejs/node (node)
v26Moved to doc/changelogs/CHANGELOG_V6.md#6.0.0.
v25Moved to doc/changelogs/CHANGELOG_V012.md#0.12.8.
v24Moved to doc/changelogs/CHANGELOG_IOJS.md#2.1.0.
v23Moved to doc/changelogs/CHANGELOG_V6.md#6.1.0.
v22Moved to doc/changelogs/CHANGELOG_V4.md#4.4.1.
v21Moved to doc/changelogs/CHANGELOG_V4.md#4.2.6.
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.