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

Dependabot bump of the Next.js runner stage base image from node:24-alpine to node:26-alpine in apps/frontend/Dockerfile. The build stage (using oven/bun:1) is untouched, and only the runtime node invocation and the inline npm install sharp@0.34.5 step are affected by this change.

• Bumps the runner stage base image from node:24-alpine to node:26-alpine in the frontend Dockerfile.
• Node 26 was released in April 2026 and is currently in "Current" status; it will not enter LTS until October 2026, which is worth noting for a production image.

Confidence Score: 4/5

The change is a single-line base image bump in the runner stage; the build stage is unaffected and the runtime behavior of the Next.js app is otherwise unchanged.

The only change is swapping node:24-alpine for node:26-alpine in a multi-stage Dockerfile. Node 26 is freshly released and not yet in LTS, which is worth flagging for a production image, but there are no logic, security, or correctness issues introduced here.

No files require special attention beyond the single-line Dockerfile change.

Important Files Changed

Filename	Overview
apps/frontend/Dockerfile	Single-line change bumping the runner stage base image from node:24-alpine to node:26-alpine; build stage remains on oven/bun:1 and is unaffected.

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 still in Current (non-LTS) status**

Node 26 was released in April 2026 and won't enter LTS until October 2026. Production images typically pin to an LTS release for longer support and stability guarantees. If the goal is to stay on an actively-maintained LTS, `node:22-alpine` (LTS through April 2027) or staying on `node:24-alpine` (LTS through April 2028) would be the safer choices until Node 26 enters LTS in October 2026.

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

[greptile-apps]

Node 26 is still in Current (non-LTS) status

Node 26 was released in April 2026 and won't enter LTS until October 2026. Production images typically pin to an LTS release for longer support and stability guarantees. If the goal is to stay on an actively-maintained LTS, node:22-alpine (LTS through April 2027) or staying on node:24-alpine (LTS through April 2028) would be the safer choices until Node 26 enters LTS in October 2026.

Prompt To Fix With AI

This is a comment left during a code review.
Path: apps/frontend/Dockerfile
Line: 51

Comment:
**Node 26 is still in Current (non-LTS) status**

Node 26 was released in April 2026 and won't enter LTS until October 2026. Production images typically pin to an LTS release for longer support and stability guarantees. If the goal is to stay on an actively-maintained LTS, `node:22-alpine` (LTS through April 2027) or staying on `node:24-alpine` (LTS through April 2028) would be the safer choices until Node 26 enters LTS in October 2026.

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!

[m43i]

Wont do it as it is not lts

[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