[16.x] build: remove windows-2022 from v16.x actions#42299
[16.x] build: remove windows-2022 from v16.x actions#42299danielleadams wants to merge 1 commit intonodejs:v16.x-stagingfrom
Conversation
|
Review requested:
|
2804f2d to
6a0ce1a
Compare
|
Fast-track has been requested by @danielleadams. Please 👍 to approve. |
|
Landed in 728b657 |
PR-URL: #42299 Reviewed-By: Jiawen Geng <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Rich Trott <[email protected]>
|
Belated +1 to this PR and unblocking the release. It looks like I am just wondering if we should open an issue to track/identify this problem? I could see the outcome potentially being that we can add it back when/if a future actions update fixes it? Or maybe opt to update BUILDING.md as I think(?) it is implicitly stating that this would be a supported toolchain for Node.js 16? |
Sure. I also tried to report the bug to MSVC team yesterday, but report bug entrance only in visual studio on windows which I don't have for now. |
PR-URL: #42299 Reviewed-By: Jiawen Geng <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Rich Trott <[email protected]>
I've already reported this bug to MSVC team issue ticket |
Removes GitHub actions run on the
windows-2022virtual environment for v16.x release line. (As mentioned here: #42200) (cc @nodejs/releasers, @gengjiawen)