chore: install specific Node version on Mac before building binary

[bahmutov]

To match the needed version from .node-version file

• probably need to set up the same Node version in multiple jobs for Mac, like build and build-binary
  blocked by the code signing error on MAc

Frameworks/Electron Framework.framework/Versions/A/Electron Framework: code object is not signed at all

[cypress-bot]

Thanks for taking the time to open a PR!

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.
• Become familiar with the Code Review Checklist for guidelines on coding standards and what needs to be done before a PR can be merged.

[cypress]

---

Test summary

8026 • 0 • 108 • 3

---

Run details

Project	cypress
Status	Passed
Commit	ff07a32
Started	Aug 11, 2020 5:18 PM
Ended	Aug 11, 2020 5:25 PM
Duration	06:23 💡
OS	Linux Debian - 10.2
Browser	Multiple

View run in Cypress Dashboard ➡️

---

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard

[flotwig]

@bahmutov this runs only on build job, right? I think we expect all tests to use the same Node version that was bundled with Electron, so that tests are using the same stdlib as they will be in Electron. So this should run on all test jobs (or at least all of the internal test jobs like server-unit-test, server-e2e-test...)

[bahmutov]

yeah, it will require more stuff to happen here, every command needs to do this nonsense

[brian-mann]

isn't this hard coding the version instead of pulling it from .node-version?

[bahmutov]

Yup it is hard coding it for now

…

Sent from my iPhone

On Aug 11, 2020, at 09:01, Brian Mann ***@***.***> wrote:  @brian-mann commented on this pull request. In circle.yml: > + nvm install v12.14.1 + nvm alias default v12.14.1 isn't this hard coding the version instead of pulling it from .node-version? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.