Skip to content

build(deps): bump node from 24-alpine to 26-alpine in /apps/frontend in the docker group across 1 directory #496

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

Closed
dependabot wants to merge 1 commit into from
Closed

build(deps): bump node from 24-alpine to 26-alpine in /apps/frontend in the docker group across 1 directory #496

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 apps/frontend/Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ COPY packages/files/src/project-file-proxy-path.ts packages/files/src/project-fi
WORKDIR /app/apps/frontend
RUN bun run build

FROM node:24-alpine AS runner
FROM node:26-alpine AS runner

@greptile-apps greptile-apps Bot Jul 6, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

P2 Node 26 is not yet LTS

node:26-alpine is the current "stable" release but has not yet received LTS designation — that is expected in October 2026. Node 24 (krypton) remains the active LTS through April 2028. Upgrading to a non-LTS release in a production runner image means shorter community-tested lifetime and potential exposure to API churn before the release stabilises. Consider waiting for Node 26 to reach LTS, or keeping node:24-alpine until then.

Prompt To Fix With AI 
This is a comment left during a code review.
Path: apps/frontend/Dockerfile
Line: 51

Comment:
**Node 26 is not yet LTS**

`node:26-alpine` is the current "stable" release but has not yet received LTS designation — that is expected in October 2026. Node 24 (`krypton`) remains the active LTS through April 2028. Upgrading to a non-LTS release in a production runner image means shorter community-tested lifetime and potential exposure to API churn before the release stabilises. Consider waiting for Node 26 to reach LTS, or keeping `node:24-alpine` until then.

How can I resolve this? If you propose a fix, please make it concise.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Fix in Claude Code Fix in Codex

WORKDIR /app

ARG BUILD_LABEL=
Expand Down