[nschonni]

Description

Building on #2650.
The build-automation.mjs now handles all the updating of the Dockerfiles, but drops the previous CLI/options.
This also removes the related special config files and supporting bash scripts.

Motivation and Context

The old update.sh had a few options around version and variants. While handy for some debugging, with the easiness of comparing the outputs, its better to just test and compare without filtering.

Testing Details

1. Run npm ci
2. Change any Dockerfile version number
3. Run npm run build
4. Any of the changed files should be reverted to the current NODE_VERSION should be pointing to the latest
5. Change any of the Node.keys values or anything in the Dockerfile. Running build shouldn't produce any diff, but warn of the missmatch non-version changes detected, but file not updated.

Example Output(if appropriate)

$ npm run build

> build
> node build-automation.mjs

Found major versions in versions.json: 22, 24, 26
Grabbing Index.json files
Checking for updates for 22
        Latest version: v22.23.4
        Released: 2026-10-20
        Security release: true
        alpine3.23: everything up to date!
        alpine3.24: everything up to date!
        bookworm: everything up to date!
        bookworm-slim: everything up to date!
        trixie: everything up to date!
        trixie-slim: everything up to date!
Checking for updates for 24
        Latest version: v24.22.1
        Released: 2026-10-20
        Security release: true
        alpine3.23: everything up to date!
        alpine3.24: everything up to date!
        bookworm: everything up to date!
        bookworm-slim: everything up to date!
        trixie: everything up to date!
        trixie-slim: everything up to date!
Checking for updates for 26
        Latest version: v26.12.1
        Released: 2026-10-21
        Security release: true
        alpine3.23: everything up to date!
        alpine3.24: everything up to date!
        bookworm: everything up to date!
        bookworm-slim: everything up to date!
        trixie: everything up to date!
        trixie-slim: everything up to date!
No Pull Request will be created.

Types of changes

• Documentation
• Version change (Update, remove or add more Node.js versions)
• Variant change (Update, remove or add more variants, or versions of variants)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Other (none of the above)

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING.md document.
• All new and existing tests passed.

[nschonni]

Unmarking as draft, as this could land instead of #2650, since it includes those changes

[MikeMcC399]

After rebasing in a test branch to drop the last update 80f02a5 and running npm run build, I saw the following dialog:

$ npm run build

> build
> node build-automation.mjs

Found major versions in versions.json: 22, 24, 26
Grabbing Index.json files
Checking for updates for 22
        Latest version: v22.23.4
        Released: 2026-10-20
        Security release: true
        alpine3.23: updating to v22.23.4
        alpine3.24: updating to v22.23.4
        bookworm: updating to v22.23.4
        bookworm-slim: updating to v22.23.4
        trixie: updating to v22.23.4
        trixie-slim: updating to v22.23.4
Checking for updates for 24
        Latest version: v24.22.1
        Released: 2026-10-20
        Security release: true
        alpine3.23: updating to v24.22.1
        alpine3.24: updating to v24.22.1
        bookworm: updating to v24.22.1
        bookworm-slim: updating to v24.22.1
        trixie: updating to v24.22.1
        trixie-slim: updating to v24.22.1
Checking for updates for 26
        Latest version: v26.12.1
        Released: 2026-10-21
        Security release: true
        alpine3.23: updating to v26.12.1
        alpine3.24: updating to v26.12.1
        bookworm: updating to v26.12.1
        bookworm-slim: updating to v26.12.1
        trixie: updating to v26.12.1
        trixie-slim: updating to v26.12.1
::set-env name=NODE_PR_TITLE::feat: Node.js v22.23.4, v24.22.1, v26.12.1

Committing that change, then rebasing on main dropped the new commit, which showed that the commit results of the new process were inline with the old process.

That's a good test result!

[MikeMcC399]

LGTM!

If you're also happy with this, let's take this PR instead of just the preliminary step of #2650

[MikeMcC399]

@nschonni

Do you want to go ahead with this one? The next Node.js release would be 26.13.0 on Wednesday, Oct 28, 2026, which will be the previous 26.12.1 release, re-tagged with the same content.

[nschonni]

@nodejs/docker how about this get's merged tomorrow if no one objects.
I'll close the other "first step" PR, and suggest this gets squash-merged to skip the package-lock.json noise. Alternately, I could just rebase this to 1 commit first

[SimenB]

nice 👍 squashing sounds good