Skip to content

Conversation

@Hweinstock
Copy link
Contributor

@Hweinstock Hweinstock commented Oct 17, 2024

Problem

There's no real reason we need to use node 16 in CI, and it's preventing us from using some features.

Our tests run against vscode's own version of node, which is unrelated to the node we use to run scripts, etc. (See also: #5761 )

Solution

update CI runners to node 18 instead of 16.
We need to pass { shell: true } to avoid error on windows. see more here: https://nodejs.org/en/blog/vulnerability/april-2024-security-releases-2


License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

@Hweinstock Hweinstock changed the title dep(ci node): update node in ci to 18.x deps(ci node): update node in ci to 18.x Oct 17, 2024
@Hweinstock
Copy link
Contributor Author

Tried bumping the vscode/electron-test version due to failing windows tests, but perhaps its unrelated. I'll continue to investigate.

@Hweinstock Hweinstock changed the title deps(ci node): update node in ci to 18.x deps(ci node): update node in ci to 18.x [WIP] Oct 18, 2024
@Hweinstock Hweinstock marked this pull request as ready for review October 21, 2024 22:00
@Hweinstock Hweinstock requested a review from a team as a code owner October 21, 2024 22:00
Copy link
Contributor

@justinmk3 justinmk3 left a comment

Choose a reason for hiding this comment

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

Nice!

We need to pass { shell: true } to avoid error on windows. see more here: https://nodejs.org/en/blog/vulnerability/april-2024-security-releases-2

related: #5292

@Hweinstock Hweinstock merged commit c6e4516 into aws:master Oct 23, 2024
22 of 24 checks passed
@Hweinstock Hweinstock deleted the cinodebump branch October 23, 2024 18:09
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.

2 participants