Skip to content

Add support for Node.js v26 prebuilds and remove EOL builds#1468

Merged
m4heshd merged 3 commits into
WiseLibs:masterfrom
m4heshd:node-26-prebuilds
May 11, 2026
Merged

Add support for Node.js v26 prebuilds and remove EOL builds#1468
m4heshd merged 3 commits into
WiseLibs:masterfrom
m4heshd:node-26-prebuilds

Conversation

@m4heshd
Copy link
Copy Markdown
Contributor

@m4heshd m4heshd commented May 6, 2026

Added support for Node.js v26 and removed EOL versions 20 and 23.

@m4heshd m4heshd requested review from a team and JoshuaWise as code owners May 6, 2026 23:21
@m4heshd
Copy link
Copy Markdown
Contributor Author

m4heshd commented May 6, 2026

Node v26 tests are failing because of yargs/yargs#2509. Deja vu 😵‍💫.

@m4heshd
Copy link
Copy Markdown
Contributor Author

m4heshd commented May 9, 2026

All good to go. Pinging @Prinzhorn.

@Prinzhorn
Copy link
Copy Markdown
Contributor

Is there a reason to keep 20/23 in the engines list?

@m4heshd
Copy link
Copy Markdown
Contributor Author

m4heshd commented May 11, 2026

I expected some people to be still using Node 20 on their stable applications, and given projects like node-nes, it was acceptable IMO. Mostly, the concern is that some CIs/builders consider the "unsupported engine" warning as an error, which would stop them from building the binaries themselves. I saw someone complaining about it.

Technically, BS3 is still fully functional on these legacy engines, so we'll keep v20 for now. We just won't be building prebuilt binaries for them. I say let's keep them in supported engines till the next LTS.

@m4heshd m4heshd merged commit a640028 into WiseLibs:master May 11, 2026
26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants