Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: use node 14 explicitly #386

Merged
merged 4 commits into from
Apr 11, 2022
Merged

fix: use node 14 explicitly #386

merged 4 commits into from
Apr 11, 2022

Conversation

WillieRuemmele
Copy link
Contributor

What does this PR do?

uses node 14 directly

What issues does this PR fix or reference?

[skip-validate-pr]

@@ -75,7 +75,7 @@ workflows:
- release-management/release-package:
sign: true
github-release: true
node_version: lts
node_version: '14'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Beware of using node v14 on windows.
We pinned v16 and v17 to known safe versions here: forcedotcom/npm-release-management-orb#93

v14 was ok then but between that pr and today maybe a new 14 with the bad npm was released and jobs will not run.

@WillieRuemmele WillieRuemmele merged commit c1ca07d into main Apr 11, 2022
@WillieRuemmele WillieRuemmele deleted the wr/explicitNode branch April 11, 2022 20:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants