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

announcement: end of support for Node.js 18.x in the Azure SDK for JavaScript #33017

Open
maorleger opened this issue Feb 12, 2025 · 2 comments
Assignees
Labels
Azure.Core Client This issue points to a problem in the data-plane of the library.
Milestone

Comments

@maorleger
Copy link
Member

maorleger commented Feb 12, 2025

After July 10, 2025, the Azure SDK for JavaScript will no longer support Node.js 18.x, which reaches end-of-life on April 30, 2025.

As a reminder of the Azure SDK for JavaScript support policy, dropping support for such Node.js versions may be done without increasing the major version of the Azure SDK libraries.

We encourage you to upgrade to an Active Node.js Long Term Support (LTS) version.

For more details, see our blog post.

@maorleger maorleger added Azure.Core Client This issue points to a problem in the data-plane of the library. labels Feb 12, 2025
@maorleger maorleger added this to the 2025-07 milestone Feb 12, 2025
@maorleger maorleger self-assigned this Feb 12, 2025
@maorleger maorleger pinned this issue Feb 12, 2025
@timtucker
Copy link

timtucker commented Feb 18, 2025

It feels like there's a major issue in alignment between Microsoft releases and Node LTS releases.

Ideal ordering for releases:

  • New Node LTS version (N) is released and becomes the "Current" version
  • MS SDKs and platforms add "Preview" support
  • LTS version becomes "Active"
  • MS SDKs and platforms have GA support
  • MS / Node remind everyone that (N-2) will be no longer supported in X months
  • Customers have months to jump from (N-2) to (N) and not need to update Node versions for 2+ years (the "long term" part of LTS)
  • Node & MS support for support for (N-2) is discontinued

The order we see happening instead:

  • New Node LTS version (N) is released and becomes the "Current" version
  • LTS release becomes the "Active" version
  • MS starts offering preview support for the new version
  • MS / Node remind everyone that (N-2) will be no longer supported in X months
  • The only supported option for customers is migrating to (N-1)
  • Node & MS support for support for (N-2) is discontinued
  • MS support for (N) is generally available

Examples:

Azure Functions still doesn't support Node 22:
Azure/azure-functions-nodejs-library#252

In the case of Static Web Apps, documentation still refers to support for Node 20 as only being in "Preview":
https://learn.microsoft.com/en-us/azure/static-web-apps/languages-runtimes

There's been an open GitHub issue noting this for months with no comment from anyone at MS:
Azure/static-web-apps#1534

@xirzec
Copy link
Member

xirzec commented Feb 18, 2025

@timtucker Definitely hear the feedback on Azure Functions and Web Apps not being well aligned with the Node LTS schedule. I can pass that along, but I think it means more coming directly from customers, especially if you file a support request: https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request

For SDK packages maintained in this repo, we try our best to test against the latest stable Node releases and are happy to resolve any issues with Node 22. You can see our current pipeline matrix here:

"NodeTestVersion": ["18.x", "20.x", "22.x"],

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Azure.Core Client This issue points to a problem in the data-plane of the library.
Projects
None yet
Development

No branches or pull requests

3 participants