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

[dependabot]

Bumps the docker group with 1 update in the /apps/frontend directory: node.

Updates node from 24-alpine to 26-alpine

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[greptile-apps]

Greptile Summary

This PR bumps the Docker runner base image for the frontend application from node:24-alpine to node:26-alpine, as generated by Dependabot.

• The change affects only the multi-stage build's final runner stage (line 51); the builder stage continues to use oven/bun:1 unchanged.
• Node.js 26 was released in May 2026 and the node:26-alpine image is available on Docker Hub, but it is still in "Current" status — LTS designation is not expected until October 2026, while Node 24 remains the active LTS.

Confidence Score: 4/5

Safe to merge if the team is comfortable adopting a non-LTS Node release; the image exists and the change is minimal.

The only concern is that Node 26 has not yet reached LTS status — it is still in its "Current" release phase and the LTS designation is expected in October 2026. Node 24 is still the active LTS with support through April 2028. Everything else in the Dockerfile (the build stage, the sharp install, the startup command) remains unchanged and is unaffected.

apps/frontend/Dockerfile — specifically the choice of Node 26 (Current, not yet LTS) as the production runner base image.

Important Files Changed

Filename	Overview
apps/frontend/Dockerfile	Bumps the runner base image from node:24-alpine to node:26-alpine; Node 26 is currently in "Current" (not yet LTS) status, otherwise the change is straightforward.

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
apps/frontend/Dockerfile:51
**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.

_{Reviews (1): Last reviewed commit: "build(deps): bump node" | Re-trigger Greptile}

[greptile-apps]

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!

[dependabot]

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml