feat: add node26 runtime images - #148
Open
catzo-agent[bot] wants to merge 1 commit into
Open
Conversation
ahiggins-arti
marked this pull request as ready for review
July 28, 2026 20:33
This comment has been minimized.
This comment has been minimized.
Author
There was a problem hiding this comment.
PR Triage: 🔴 High risk. Needs human review.
Reviewers: @articulate/devex
Why
Risk
- 26/base/Dockerfile: adds build-system configuration for a published runtime container image → High
- README.md: documents the new image tag → Low
- Highest risk across files wins → High
Reviewers
CODEOWNERS .github/CODEOWNERS catch-all * → @articulate/devex
Code Review: ✅ Approved
The Node 26 image follows the established Node 24 image structure, and its multi-architecture build and lint checks pass. Residual risk is limited to publishing a new major runtime tag.
👍 👎 or quote this comment to provide feedback. · reviewed 93bc8a5 · openai/gpt-5.6-sol-fast
dholmes
reviewed
Jul 28, 2026
|
|
||
| > 🌟 recommended image | ||
|
|
||
| * __articulate/node:26__ 🌟 |
Contributor
There was a problem hiding this comment.
nit: I'd consider removing the recommended 🌟 until it is LTS
ahodges22
approved these changes
Jul 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The working tree is now clean and consistent. I couldn't run
hadolint(the CI linter) locally as it isn't installed, but the remaining26/base/Dockerfileis byte-for-byte structurally identical to the passing24/base/Dockerfile(only theFROMtag differs), and I verifiednode:26-bookworm-slimexists on Docker Hub.Summary
feat: add node26 base runtime image
Adds a Node 26 base image following the existing pattern:
26/base/Dockerfile—articulate/node:26, builtFROM node:26-bookworm-slim. Includes the docker-bootstrap entrypoint, secrets helper,install_packages, AWS CLI, AWS RDS CA trust bundle (split and installed viaupdate-ca-certificates), a non-rootserviceuser/group (UID/GID 1001), Corepack,make,dumb-init, andwait-for-it.sh.README.md— listsarticulate/node:26🌟 under Tags.No Lambda variant. The
26-lambdaimage was deferred: its base,public.ecr.aws/lambda/nodejs:26, does not yet exist in the public ECR registry (the manifest endpoint returns404 MANIFEST_UNKNOWN, versus200for tags24and22). Because CI discovers everyDockerfileviafindand builds it, including a Lambda Dockerfile pointing at a non-existent base would break every build/publish run. It should be added once AWS publishes a Node 26 Lambda runtime.Source: n8n:catzo-slack-build (slack)
Agent session: 📊 Datadog · this job
Model:
anthropic/claude-opus-4-8(reasoning:xhigh)Adversarial Critic:
codex/openai/gpt-5.6-terra