chore(deps): bump node from 22-alpine to 25-alpine - #72
Conversation
Bumps node from 22-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>
|
Closing in favour of #73. Node 25 reached end of life on 2026-06-01 — 82 days before this PR was The seven green checks here were all true and none of them was about the thing #73 moves both stages to |
|
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. |
…#73) Dependabot PR #72 proposed node:22-alpine -> node:25-alpine. Node 25 is a Current (odd-numbered) release that reached END OF LIFE on 2026-06-01, per nodejs/Release schedule.json — so that bump would have pinned the published container to a runtime receiving no further security patches, five days short of three months after EOL. CI was green because the workflows test the packed npm artifact on Node 18/20/22/24 and never build the Dockerfile. Bump to node:24-alpine instead (Krypton, Active LTS, maintenance 2026-10-20, end 2028-04-30) and tell Dependabot to stop proposing Node majors so the next one is a deliberate move to v26 when it becomes Active LTS on 2026-10-28. Digest-level minor/patch refreshes on the pinned major still come through. Verified locally on 2026-08-22: docker build ... -> success docker run --entrypoint node -> v24.19.0 MCP stdio initialize -> serverInfo {"name":"oilpriceapi","version":"3.2.3"} Closes #72 Claude-Session: https://claude.ai/code/session_01JKAExynd9zoKwt6rYA66EA Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Bumps node from 22-alpine to 25-alpine.
Most Recent Ignore Conditions Applied to This Pull Request
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)