fix: correct update script to support version argument again #2156
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We keep getting key updates from the update script for unchanged node versions, even when the script passes e.g.
./update.sh 22
. This is due to a regression in #1307 where theget_versions
function no longer looked at its arguments for which version directories to load.I also got
./update.sh: line 240: pids[@]: unbound variable
, so I moved its declaration.I also couldn't resist
Object.keys() -> Object.entires()
since we were accessing the values in the loopThis should remove the need for PRs such as #2151, as the script should just update the versions with an actual node version change:
docker-node/build-automation.mjs
Line 92 in ebd48c9