chore(deps): bump node from 22-bookworm-slim to 26-bookworm-slim in /docker in the docker group#557
Conversation
Bumps the docker group in /docker with 1 update: node. Updates `node` from 22-bookworm-slim to 26-bookworm-slim --- updated-dependencies: - dependency-name: node dependency-version: 26-bookworm-slim dependency-type: direct:production dependency-group: docker ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
github-actions
Bot
added
area: ci
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4d48892494
ℹ️ 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".
| # Keep the Docker base on Node 22 because the official Node 24/25 slim images | ||
| # no longer publish linux/arm/v7 manifests, which breaks our armv7 Docker jobs. | ||
| FROM node:22-bookworm-slim AS builder | ||
| FROM node:26-bookworm-slim AS builder |
There was a problem hiding this comment.
When the existing CI/release Docker matrix builds linux/arm/v7 (.github/workflows/ci.yml and release.yml both still include arch: armv7), Buildx has to resolve this FROM image for arm/v7 before any Dockerfile logic runs. The file comment and the checked-in guard test (scripts/dev/docker.workflow.test.ts, uses an armv7-capable node base image) document that the Node 22 slim base is intentional for those armv7 jobs, and this change makes that test fail while leaving the armv7 publish path enabled.
Useful? React with 👍 / 👎.
Bumps the docker group in /docker with 1 update: node.
Updates
nodefrom 22-bookworm-slim to 26-bookworm-slimDependabot 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 <dependency name> major versionwill 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 versionwill 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