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

doc: update Windows and VS support tables #3049

Merged
merged 2 commits into from
Oct 10, 2022

Conversation

targos
Copy link
Member

@targos targos commented Oct 7, 2022

This removes rows for unsupported Node.js versions and removes support
for building addons with VS2015 starting with Node.js 19.0.0.

This removes rows for unsupported Node.js versions and removes support
for building addons with VS2015 starting with Node.js 19.0.0.
@targos
Copy link
Member Author

targos commented Oct 7, 2022

I think this is something we should do regardless of issues with V8, to prepare users for Node.js 20. Visual Studio 2015 will be out of support on Oct 14, 2025, before the 20.x EoL.

@targos
Copy link
Member Author

targos commented Oct 8, 2022

@nodejs/build

@gengjiawen
Copy link
Member

@Trott Can you merge this ? thx

Copy link
Member

@richardlau richardlau left a comment

Choose a reason for hiding this comment

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

For the CI to reflect this VersionSelectorScript.groovy will need to be updated to exclude the configurations for VS2015

// VS versions supported to build add-ons
[ /vs2013-COMPILED_BY/, testType, gte(9) ],
[ /vs2015-COMPILED_BY/, testType, noVer ],
[ /vcbt2015-COMPILED_BY/, testType, noVer ],
[ /vs2017-COMPILED_BY/, testType, lt(8) ],
[ /vs2019-COMPILED_BY/, testType, lt(12) ],

@targos
Copy link
Member Author

targos commented Oct 10, 2022

@richardlau I just updated that file.

@richardlau richardlau merged commit e6f5be4 into nodejs:main Oct 10, 2022
@targos targos deleted the bye-bye-vs2015 branch October 10, 2022 10:54
@targos
Copy link
Member Author

targos commented Oct 10, 2022

I this deployed to jenkins automatically?

@richardlau
Copy link
Member

The CI always pulls the version of the selector script from main of this repository.

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.

4 participants