You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<smallclassName="!text-xs">for Node.js 18 and below</small>
23
+
</Button>
24
+
</div>
25
+
15
26
## What Happens When a Release Line Reaches EOL
16
27
17
28
When a version reaches End-Of-Life, it means that it will no longer receive updates, including security patches. This can leave applications running on these versions vulnerable to security issues and bugs that will never be fixed.
@@ -32,16 +43,3 @@ Despite the obvious downsides of using EOL releases, in practice, organizations
32
43
Node.js currently partners with HeroDevs to provide Never-Ending Support (NES) for Node.js versions past their official maintenance phase. This includes security patches, compliance assistance, and technical support to help bridge the gap while you plan your upgrade strategy. For more detailed information, visit the [**HeroDevs Node.js NES page**](https://www.herodevs.com/support/node-nes?utm_source=NodeJS+&utm_medium=Link&utm_campaign=Nodejs_eol_support).
33
44
34
45
Using EOL releases through NES should be viewed as a temporary solution—the goal should always be to upgrade to actively supported versions.
0 commit comments