René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Prepare for Node.js 26 release Apr 2026","articleBody":"## Situation\n\nAccording to [schedule.json](https://github.com/nodejs/Release/blob/main/schedule.json) the `v26` release of Node.js is planned for 2026-04-22.\n\n## Assessment\n\nReviewing [versions.json](https://github.com/nodejs/docker-node/blob/main/versions.json) in this repo and [BUILDING.md](https://github.com/nodejs/node/blob/main/BUILDING.md) document in the `node` repo by executing:\n\n```shell\ngit diff v25.x main -- BUILDING.md\n```\n\nshows no platforms specified in [versions.json](https://github.com/nodejs/docker-node/blob/main/versions.json) as being dropped in the default `main` branch of [node](https://github.com/nodejs/node), so it should not be necessary to drop any platforms in [versions.json](https://github.com/nodejs/docker-node/blob/main/versions.json) for the Docker builds.\n\n[Debian releases](https://www.debian.org/releases/) shows Debian 13 (trixie) as the current \"Stable\" release with End of LTS on 2030-06-30, which is after the planned EOL of Node.js 26 on 2029-04-30. Debian 12 (bookworm) End of LTS 2028-06-30 \u0026 Debian 11 (bullseye) End of LTS 2026-08-31 dates are earlier than EOL of Node.js 26.\n\n[Alpine Linux](https://alpinelinux.org/releases/) shows v3.21 - v3.23 as supported when Node.js is released.\n\n## Suggestions\n\nFor the upcoming Node.js 26 release:\n\n- Change default from Debian 12 (bookworm) to Debian 13 (trixie)\n\n    | Item             | 25         | 26       |\n    | ---------------- | ---------- | -------- |\n    | `debian-default` | `bookworm` | `trixie` |\n\n- Drop `oldoldstable` \u0026 `oldstable` Debian builds\n\n    I suggest to drop builds for Debian 11 (bullseye / bullseye-slim / oldoldstable) \u0026 Debian 12 (bookworm / bookworm-slim / oldstable) for Node.js 26 and build only for Debian 13 (trixie / stable), unless there is a compelling reason to continue with the `oldoldstable` \u0026 `oldstable` releases. This significantly reduces the number of build combinations. See also https://github.com/nodejs/docker-node/issues/2398 regarding defining a strategy for Debian releases.\n\n- For Alpine, continue with v3.22 \u0026 v3.23 and with `alpine-default` as `alpine3.23`\n\n- Add dates from [schedule.json](https://github.com/nodejs/Release/blob/main/schedule.json)\n\n    ```json\n    \"v26\": {\n        \"start\": \"2026-04-22\",\n        \"lts\": \"2026-10-28\",\n        \"maintenance\": \"2027-10-20\",\n        \"end\": \"2029-04-30\",\n        \"codename\": \"\"\n    }\n    ```\n","author":{"url":"https://github.com/MikeMcC399","@type":"Person","name":"MikeMcC399"},"datePublished":"2026-03-30T09:56:34.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":9},"url":"https://github.com/2435/docker-node/issues/2435"}