chore(deps): bump node from 24-alpine to 25-alpine in /deploy/docker - #95
chore(deps): bump node from 24-alpine to 25-alpine in /deploy/docker#95dependabot[bot] wants to merge 1 commit into
Conversation
Bumps node from 24-alpine to 25-alpine. --- updated-dependencies: - dependency-name: node dependency-version: 25-alpine dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 65dd0873ee
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| @@ -1,4 +1,4 @@ | |||
| FROM node:24-alpine@sha256:a0b9bf06e4e6193cf7a0f58816cc935ff8c2a908f81e6f1a95432d679c54fbfd AS build | |||
| FROM node:25-alpine@sha256:bdf2cca6fe3dabd014ea60163eca3f0f7015fbd5c7ee1b0e9ccb4ced6eb02ef4 AS build | |||
There was a problem hiding this comment.
Do not build artifacts with EOL Node 25
As of July 31, 2026, the official Node release table marks v25 as EOL while v24 remains LTS (https://nodejs.org/en/about/previous-releases), so this build stage would install dependencies and generate the static site with an unsupported runtime. The rest of the repo also still enforces the Node-24 toolchain (tests/config/toolchain-versions.test.ts expects this Dockerfile to contain node:24-alpine, and CI runs pnpm verify), so this single-line Docker dependency bump is both non-releasable and a downgrade in security support; keep 24 or move every manifest/workflow/test to a supported line together.
Useful? React with 👍 / 👎.
Bumps node from 24-alpine to 25-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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)