-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
[16.x] build: remove windows-2022 from v16.x actions #42299
[16.x] build: remove windows-2022 from v16.x actions #42299
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 <technicalcute@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
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 <technicalcute@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
I've already reported this bug to MSVC team issue ticket |
Removes GitHub actions run on the
windows-2022
virtual environment for v16.x release line. (As mentioned here: #42200) (cc @nodejs/releasers, @gengjiawen)