JS-941 Fix: Disable all Node.js binaries in "without node" jobs #5900
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.





JS-941
Summary
Fix the "without node" jobs to properly disable ALL Node.js binaries, ensuring
EmbeddedNode.javadeploys the embedded Node.js runtime.Problem
The "without node" jobs were not showing "Deployed node version" in their logs, meaning they were using host Node.js instead of the embedded version.
The previous
remove_node_from_pathstep only disabled the first node binary found bywhich, but runners can have multiple node binaries:/home/runner/.local/share/mise/installs/node/22.11.0/bin/node/usr/bin/nodeor elsewhereAfter disabling the first one,
which nodewould find another, so SonarJS still detected node and didn't deploy the embedded version.Changes
Expected Result
After this fix, the "without node" jobs should show "Deployed node version" messages in their logs, confirming that
EmbeddedNode.javais deploying the embedded Node.js runtime.Test plan
🤖 Generated with Claude Code