-
Notifications
You must be signed in to change notification settings - Fork 210
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
add setup node to finalize-release.yaml #7409
Conversation
this is the only place where we need to do this? |
most of our ado pipelines already have this for core already. Otherwise I'm pretty sure we would have experienced breakages from Gytis' PR. |
linking https://github.com/actions/runner-images/blob/main/images/ubuntu/Ubuntu2204-Readme.md as an fyi re what ver of node is being used by the image |
@Mergifyio backport release/4.10.x release/4.11.x |
✅ Backports have been created
|
Co-authored-by: Daniel Rodriguez <[email protected]> (cherry picked from commit 1fbf7df)
Co-authored-by: Daniel Rodriguez <[email protected]> (cherry picked from commit 1fbf7df)
…1.x] (#7420) Co-authored-by: Daniel Rodriguez <[email protected]>
…0.x] (#7419) Co-authored-by: Daniel Rodriguez <[email protected]>
Add setup node step to pipeline. Otherwise we run the risk of a vm not using a supported version of node.
This caused an error in another pipeline, so we should use node setup or nodeTool whenever possible to avoid this problem