deps(docker)(deps): bump node from 20-slim to 26-slim in /frontend#25
deps(docker)(deps): bump node from 20-slim to 26-slim in /frontend#25dependabot[bot] wants to merge 1 commit into
Conversation
Bumps node from 20-slim to 26-slim. --- updated-dependencies: - dependency-name: node dependency-version: 26-slim dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
…end, and CI Node 20 LTS hits EOL April 2026. Bumping the entire build matrix to 26-slim in one PR so CI and the Docker base stay aligned — running the test suite on a different node than production is the exact gap that masks "works locally / works in CI / breaks in prod" Node-API incompatibilities. Changes: - backend/Dockerfile: builder + runtime stages -> node:26-slim - frontend/Dockerfile: deps + builder + runtime stages -> node:26-slim - 11 workflow files: setup-node node-version: 20 -> 26 (changeset-check, ci [x3], e2e, lighthouse, mutation, release, security, storybook, supply-chain) Folds in #25 (frontend Dockerfile bump) since it would have been a trivial follow-up rebase. Smoke test deferred to CI — every workflow now exercises Node 26 so any deprecation or API removal between 20 and 26 surfaces in the mandatory checks rather than waiting for a deploy. Signed-off-by: dependabot[bot] <support@github.com>
|
Folded into #26 — that PR now covers both backend and frontend Dockerfiles plus all setup-node@v* node-version pins, so CI and prod stay aligned on Node 26. |
|
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. |
1 participant
Bumps node from 20-slim to 26-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)