Skip to content

chore(deps): bump library/node from 22-bookworm-slim to 26-bookworm-slim in /apps/api - #1790

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/docker/apps/api/library/node-26-bookworm-slim
Open

chore(deps): bump library/node from 22-bookworm-slim to 26-bookworm-slim in /apps/api#1790
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/docker/apps/api/library/node-26-bookworm-slim

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 10, 2026

Copy link
Copy Markdown
Contributor

Bumps library/node from 22-bookworm-slim to 26-bookworm-slim.

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps library/node from 22-bookworm-slim to 26-bookworm-slim.

---
updated-dependencies:
- dependency-name: library/node
  dependency-version: 26-bookworm-slim
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file docker Pull requests that update docker code labels Aug 10, 2026
@sonarqubecloud

Copy link
Copy Markdown

@codspeed-hq

codspeed-hq Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Merging this PR will not alter performance

✅ 6 untouched benchmarks


Comparing dependabot/docker/apps/api/library/node-26-bookworm-slim (fc4df57) with main (3117585)

Open in CodSpeed

simple-agent-manager Bot pushed a commit that referenced this pull request Aug 17, 2026
Brings #1801, #1790, #1792, #1796 in as one reviewable unit and fixes what
each Dependabot commit left half-done.

#1801 @agentclientprotocol/sdk 0.25.0 -> 1.3.0: REMOVED instead of bumped.
An exhaustive sweep (all file types, tsconfig paths/types, vite/vitest/eslint
configs, every workspace package.json, Go modules) found zero importers.
packages/acp-client hand-rolls its ACP payload types in
src/hooks/useAcpMessagePayloads.ts and src/transport/types.ts, and
transport/websocket.ts deliberately types the ACP payload as `unknown`. The
canonical wire contract lives in the Go VM agent. Carrying a 1.3.0 dep whose
deprecated ClientSideConnection/ndJsonStream surface implies an integration
that does not exist is worse than carrying none. AGENTS.md claimed the SDK
"defines the ACP wire protocol types" — corrected to describe reality.

#1790 node 22 -> 26-bookworm-slim: taken, comment desync fixed. None of the
seven globally-installed agent CLIs declares an engines.node upper bound, so
no EBADENGINE is possible; the digest resolves to node 26.7.0 and bookworm is
still published for 26.

#1792 cloudflare/sandbox 0.12.1 -> 0.12.5: Dependabot moved only the image.
The npm client stayed at ^0.12.1 while the Dockerfile comment still asserted
they MUST match. Pinned @cloudflare/sandbox to exactly 0.12.5 — an exact pin,
because a range lets the client drift from the digest-pinned image on any
unrelated install.

#1796 @astrojs/starlight 0.40.0 -> 0.41.7: root cause of all five red checks
was peer astro@^7.0.2 vs pinned astro@6.4.8. The newer peer graph pulls
@astrojs/mdx@7.0.5, which imports `chunkToString` from
astro/runtime/server/index.js — absent in Astro 6. Upgraded astro to 7.2.2
(pinned in exactly one place, apps/www). Astro 7's rolldown pipeline then
resolves dynamic imports inside processed <script> blocks, so the mermaid
lazy-loader in BlogPost.astro needed is:inline; /scripts/blog-mermaid.js is
an esbuild output emitted to public/ at build time, i.e. a runtime URL rather
than a resolvable module. Build is clean: 181 pages + Pagefind + sitemap.

Also corrects a bad @types/node resolution combo the lockfile text-merge
produced across the two npm PRs.

Process fix: the existing Docker governance test asserted digest pinning only,
so it passed straight through BOTH stale-comment bugs. Adds two tests to
scripts/quality/dependency-governance.test.ts — reviewed-source-tag comments
must match their FROM tag, and @cloudflare/sandbox must be an exact pin equal
to the image tag. Both verified discriminating: each goes red on the exact
pre-fix state Dependabot produced.
@simple-agent-manager

Copy link
Copy Markdown
Contributor

Blocking this from merge after major-version review.

What I checked:

  • gh pr view 1790, gh pr checks 1790, and full gh pr diff 1790.
  • Upstream Node major-release notes for the 22 → 26 jump, especially Node 25 and Node 26 semver-major removals/deprecations.
  • Repo/package engine constraints and direct uses of Node APIs removed or newly runtime-deprecated across Node 25/26.
  • The exact changed file in this PR.

Why this cannot merge yet:

  1. CI is not green. Preflight Evidence is failing. The failed job log says:

    Missing or malformed Agent Preflight block markers in PR body.

  2. The diff changes only apps/api/Dockerfile.vm-agent-container; there is no .node-version change, and the GitHub Actions/node setup remains on Node 22. So this is not a repo-wide Node 22 → 26 bump; it is specifically an instant VM-agent container runtime base-image bump.

  3. The Dockerfile provenance comment is now stale:

    # Reviewed source tag: docker.io/library/node:22-bookworm-slim
    FROM docker.io/library/node:26-bookworm-slim@sha256:cd565714d4da3e84bfd341e31448f81d47c6362198f152345297c9c1154e6341

    That comment should be updated to the reviewed Node 26 source tag/digest evidence, or removed if it is no longer authoritative.

  4. Node major-change risk needs explicit runtime evidence before this production container base changes. Official Node sources note:

Local compatibility findings:

  • Root package.json has engines.node: >=20.0.0, so Node 26 is not excluded by the repo engines field.
  • I found no direct repo source usage of the Node 25/26 removed APIs in the narrowed scan.
  • The global npm CLIs installed by this Dockerfile that expose npm engines do not appear to pin specifically to Node 22; examples checked include @agentclientprotocol/claude-agent-acp@0.58.1 (>=22), @anthropic-ai/claude-code@2.1.207 (>=22.0.0), @openai/codex@0.144.6 (>=16), and @google/gemini-cli@0.50.0 (>=20).

What needs to be addressed before merge:

  • Fix the PR body/preflight evidence so CI is fully green.
  • Update the Dockerfile Reviewed source tag comment to match the Node 26 base image review.
  • Add explicit runtime validation evidence for the Node 26 VM-agent container: image builds, global npm installs complete, the installed agent binaries start under Node 26, and vm-agent bootstrap/heartbeat smoke passes.
  • Explicitly verify/package-manager expectations. Crossing Node 25 means bundled Corepack availability changes; if the instant runtime is expected to provide corepack, pnpm, or yarn to agents/workspaces, install it explicitly or document/prove that absence is acceptable.
  • Clarify whether using Node 26 while it is Current (not yet LTS) is intentional for this production runtime image.

I did not merge because CI is red and the runtime evidence above is missing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file docker Pull requests that update docker code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants