[nschonni]

Description

Took the concepts from #2581 and was able to simplify it further, now that there isn't a different source for the built versions.

Motivation and Context

This is another incremental step that should be the last one before the update.sh/function.sh scripts can be removed.

• Use ShellJS for better GitBash compat than process spawn calls for remaining update.sh use
• Use the GItHub Action library to pass/set the ENV for the GitHub Action
• Add additional logging for local troubleshooting

Testing Details

Example Output(if appropriate)

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]

Created 2 other branches just to do some "tests"

• A run with no changes, EX: the current repo state (even though a rebuild will change the Dockerfiles) https://github.com/nschonni/docker-node/actions/runs/38078159488/job/114289379485
• An example of the build when there is a change detected https://github.com/nschonni/docker-node/actions/runs/38077924120/job/114288700108

[MikeMcC399]

Could we use versions.json as the source of truth for which Node.js release lines are active?

[nschonni]

Good idea, I've changed that and cleaned up some of th ENV parts.
That GitHub thing to set the env appears to just be a print message to the log ::set-env name=NODE_PR_TITLE::feat: Node.js v26.11.1, so it could probably be inlined without taking on the dependency

The JSON parsing is a little hacky. Might be better to change the versions.json to an array with typed classes later, but doesn't make sense to make that change with this

[nschonni]

Opend #2659 as a draft to share the follow-on ideas for the migration, but that could just replace this too.

[SimenB]

nice!

[nschonni]

Gave this a rebase, but didn't do it on the follow-on PR yet