René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Prepare for Node.js 27 pre-release (Alpha) / release","articleBody":"## Task\n\nPrepare for the new Node.js release model for Node.js 27 beginning in Oct 2026 with releases like `27.0.0-alpha.1` followed 6 months later in April 2027 by `27.0.0`.\n\n## Background\n\nThe blog post [Evolving the Node.js Release Schedule](https://nodejs.org/en/blog/announcements/evolving-the-nodejs-release-schedule), March 10, 2026, announced the plan to release Node.js 27 Alpha in Oct 2026, followed by Node.js 27.0.0 in April 2027 and included the schedule information for the new model that Node.js 27 is planning to follow:\n\n| Milestone    | Date         |\n| ------------ | ------------ |\n| Alpha begins | October 2026 |\n| 27.0.0       | April 2027   |\n| Enters LTS   | October 2027 |\n| End of Life  | April 2030   |\n\nAccording to the blog post, Alpha versioning follows `semver` prerelease format (e.g., `27.0.0-alpha.1`) and `semver-major` changes are allowed during this phase.\n\n## Implications\n\nThis repo uses a combination of JavaScript, Bash script and GitHub Actions workflows to detect new Node.js versions and to update Dockerfiles to pass on to the official Docker site for image publication.\n\nIt interfaces with sources:\n- https://nodejs.org\n- https://unofficial-builds.nodejs.org\n  \nand posts its results to:\n- https://nodejs/official-images\nfor image publication.\n\nIf the existing source interfaces are extended so they publish prerelease versions such as `27.0.0-alpha.1`, then the viability of the workflows in this repo is uncertain, whichever of the following scenarios is followed:\n\n### Scenario 1 - ignore prerelease versions\n\nScript changes would be needed to ignore prerelease versions. Sorting and comparisons may produce the wrong results when prerelease and release versions are available.\n\n### Scenario 2 - publish prerelease versions\n\nTo publish prerelease (Alpha) versions as Docker images, more extensive changes would be needed. `versions.json` needs a new field for the Alpha phase. Functionality similar to the npm package [semver](https://www.npmjs.com/package/semver) would be needed for version comparisons. The full version would need to be preserved in various places, instead of using an assumption that only `major.minor.patch` formats need to be handled.\n\n## Next steps\n\nGather inputs and make a decision on the direction to be taken for Node.js 27:\n - Scenario 1 - ignore prerelease Node.js 27\n - Scenario 2 - publish prerelease Node.js 27 versions as `node` Docker images\n\nSince this is a major policy decision, it should have the active involvement of the [Docker Maintainers](https://github.com/nodejs/docker-node/blob/main/README.md#docker-maintainers), possibly also with guidance from the Node.js TSC.\n","author":{"url":"https://github.com/MikeMcC399","@type":"Person","name":"MikeMcC399"},"datePublished":"2026-05-27T15:19:31.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":11},"url":"https://github.com/2524/docker-node/issues/2524"}