From e174af464291e359422b78d3d2696ab15bc74d36 Mon Sep 17 00:00:00 2001 From: Brian Muenzenmeyer Date: Wed, 22 Oct 2025 13:27:46 -0500 Subject: [PATCH] Remove NodeSource security support reference Removed mention of NodeSource's security support for EOL Node.js versions. Signed-off-by: Brian Muenzenmeyer --- apps/site/pages/en/about/eol.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/apps/site/pages/en/about/eol.mdx b/apps/site/pages/en/about/eol.mdx index e2d2cea883c5c..7860f6ecd360c 100644 --- a/apps/site/pages/en/about/eol.mdx +++ b/apps/site/pages/en/about/eol.mdx @@ -41,6 +41,4 @@ Despite the obvious downsides of using EOL releases, in practice, organizations HeroDevs provides [Never-Ending Support (NES)](https://nodejs.org/esp/herodevs) 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. -NodeSource provides [security support](https://nodesource.com/services/support) for running older, unsupported versions of Node.js, giving teams more time and flexibility to transition to newer releases while maintaining a secure posture. - Using EOL releases through commercial support should be viewed as a temporary solution—the goal should always be to upgrade to actively supported versions.