The merge tool will currently check out other branches, such as patch, LTS etc. For that the node versions could be different and breaking. This currently results in some inconvenient Yarn install engines error mid-publishing in a way where recovering is rather cumbersome..
We should run nvm automatically, gracefully as not everbody might have it. If it fails, we print a warning and proceed running the Yarn install. That one could still fail in such cases, but this is expected then.
Note: We have considered using the Bazel-managed Node version (that would be ideal).. but we cannot let Bazel install the node modules as Bazel itself is actually made available through the @bazel/bazelisk package (caretaker might not have the proper Bazel version globally installed; if at all)
The merge tool will currently check out other branches, such as patch, LTS etc. For that the node versions could be different and breaking. This currently results in some inconvenient Yarn install engines error mid-publishing in a way where recovering is rather cumbersome..
We should run
nvmautomatically, gracefully as not everbody might have it. If it fails, we print a warning and proceed running the Yarn install. That one could still fail in such cases, but this is expected then.Note: We have considered using the Bazel-managed Node version (that would be ideal).. but we cannot let Bazel install the node modules as Bazel itself is actually made available through the
@bazel/bazeliskpackage (caretaker might not have the proper Bazel version globally installed; if at all)