chore(deps): Bump node from 20-slim to 25-slim in /docker - #156
chore(deps): Bump node from 20-slim to 25-slim in /docker#156dependabot[bot] wants to merge 1 commit into
Conversation
Bumps node from 20-slim to 25-slim. --- updated-dependencies: - dependency-name: node dependency-version: 25-slim dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
|
Closing in favor of #161, which moves the base image to
Node 24 (Krypton) is Active LTS through 2028-04-30. #161 makes that move, and also updates CI's Not your fault, Dependabot — you pick the highest tag and have no concept of Node's release lines. #161 adds a |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
The frontend-builder stage sat on node:20-slim, which went EOL on 2026-04-30 and no longer receives security patches. Dependabot noticed and proposed node:25-slim (#156) -- but 25 is an odd-numbered "Current" release that never becomes LTS and reached EOL on 2026-06-01, so that bump swapped one unpatched base image for another. Node 24 (Krypton) is Active LTS: supported until 2028-04-30, and it does not even enter maintenance until 2026-10-20. Dependabot picks the highest published tag and has no concept of Node's release lines, so it will keep proposing odd majors (26 arrives 2026-10-28, 27 a year later). Ignore semver-major bumps for `node` in the docker ecosystem and pick Node majors by hand on the LTS cadence; minor/patch bumps, which carry the base-image CVE fixes this ecosystem entry was added for, keep flowing untouched. CI's setup-node pin moves 20 -> 24 in the same change: left behind, it would typecheck and build the frontend on a different major than the shipped image builds it with. The two `node:20-slim` strings in tests/image/test_docker_image.py and the one in dependabot.yml's own comment are updated to match. Supersedes #156.
1 participant
Bumps node from 20-slim to 25-slim.
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)