v2.0.1+node25.8.1 — Node.js 25 Maintenance Patch
Runtime Node v2.0.1+node25.8.1
Secure, Distroless, Multi-Arch Node.js Runtime. Built from Scratch.
This is the first patch release on the Node.js 25 maintenance line. The Node.js runtime version remains at 25.8.1 — the image is identical to v2.0.0+node25.8.1. This release adds automated Dependabot monitoring for the develop-v1+node24 maintenance branch alongside the existing develop monitoring, constrained to minor and patch updates only.
Pull the Image
# Docker Hub — versioned (recommended for production)
docker pull runtimenode/runtime-node:v2.0.1+node25.8.1
# GitHub Container Registry — versioned (recommended for production)
docker pull ghcr.io/runtimes-node/runtime-node:v2.0.1+node25.8.1What's Included
| Component | Detail |
|---|---|
| Base | FROM scratch — no OS, no shell |
| Node.js Version | 25.8.1 (from node:25.8.1-alpine3.23) |
NODE_ENV |
production (baked in) |
TZ |
UTC (baked in) |
| Timezone Database | IANA tzdata (/usr/share/zoneinfo) |
| CA Certificates | Included (/etc/ssl/certs/) |
| DNS Resolution | nsswitch.conf included |
| Runtime Libraries | ld-musl, libstdc++, libgcc_s |
/tmp |
Writable, sticky-bit 1777 |
| Shell | None |
| Package Manager | None |
| Vulnerabilities | 0 known |
| Architectures | linux/amd64, linux/arm64 |
| Provenance & SBOM | Attached to this release |
What's New
- Added a second
updatesentry to.github/dependabot.ymltargetingdevelop-v1+node24as thetarget-branch, with adailyschedule and anignorerule suppressing allversion-update:semver-majorupdates — ensuring Dependabot only proposes minor and patch-level base image bumps against the Node.js 24 maintenance branch and never promotes it to Node.js 25 or beyond. - Applied the
v1+node24-maintenancelabel to the new Dependabot block, distinguishing its PRs from those targetingdevelop.
Maintenance Line
This tag is published on the maintenance/v2+node25 branch. The v2.x.x+node25.x.x line receives minor and patch updates only — no major Node.js version changes will be made on this branch.
Versioning
Tags follow the pattern v<image_semver>+node<node_version>. The latest tag tracks the most recent stable release on main and is not updated by maintenance releases.
Immutable Tag
This tag is immutable. Once published, v2.0.1+node25.8.1 will never be moved or overwritten on either registry.