From 11113c9340d61da23c6f046e90d73a804a62b300 Mon Sep 17 00:00:00 2001 From: bmuenzenmeyer Date: Tue, 14 Oct 2025 09:53:38 -0400 Subject: [PATCH 1/2] wip: add new ESP partner --- apps/site/pages/en/about/eol.mdx | 4 +++- apps/site/pages/en/about/partners.mdx | 2 +- apps/site/public/static/partners/constants.json | 7 +++++++ packages/i18n/src/locales/en.json | 2 +- 4 files changed, 12 insertions(+), 3 deletions(-) diff --git a/apps/site/pages/en/about/eol.mdx b/apps/site/pages/en/about/eol.mdx index 1df997c3c72e8..695f5be6f7bc1 100644 --- a/apps/site/pages/en/about/eol.mdx +++ b/apps/site/pages/en/about/eol.mdx @@ -15,7 +15,7 @@ Major versions of Node.js are released, patched, and designated End-Of-Life on a Upgrade to the latest LTS Node.js® or - @@ -42,3 +42,5 @@ Despite the obvious downsides of using EOL releases, in practice, organizations 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://nodejs.org/esp/herodevs). Using EOL releases through NES should be viewed as a temporary solution—the goal should always be to upgrade to actively supported versions. + +Node.js also partners with NodeSource... `` diff --git a/apps/site/pages/en/about/partners.mdx b/apps/site/pages/en/about/partners.mdx index be4fe2f3dc61a..1d524d8873ba9 100644 --- a/apps/site/pages/en/about/partners.mdx +++ b/apps/site/pages/en/about/partners.mdx @@ -35,7 +35,7 @@ The program provides access to security patches, compliance assistance, and tech to help bridge the gap while you plan your upgrade strategy. For more information about End-Of-Life versions, please visit [End-Of-Life Node.js Releases](/about/eol) -> Using EOL releases through NES should be viewed as a temporary solution, the goal should always +> Using EOL releases through commercial support should be viewed as a temporary solution, the goal should always > be to upgrade to actively supported versions. diff --git a/apps/site/public/static/partners/constants.json b/apps/site/public/static/partners/constants.json index fcb3a733d7cac..e866f83a8fa32 100644 --- a/apps/site/public/static/partners/constants.json +++ b/apps/site/public/static/partners/constants.json @@ -33,5 +33,12 @@ "href": "https://microsoft.com", "categories": ["infrastructure"], "weight": 2 + }, + { + "id": "NODESOURCE", + "name": "NodeSource", + "href": "https://nodesource.com/", + "weight": 3, + "categories": ["security", "esp", "release"] } ] diff --git a/packages/i18n/src/locales/en.json b/packages/i18n/src/locales/en.json index 75575f4491ece..653bd8f5e775c 100644 --- a/packages/i18n/src/locales/en.json +++ b/packages/i18n/src/locales/en.json @@ -183,7 +183,7 @@ "ltsVersionFeaturesNotice": "Want new features sooner? Get the latest Node.js version instead and try the latest improvements!" }, "eolAlert": { - "message": "Commercial support for versions past the Maintenance LTS phase is available through our OpenJS Ecosystem Sustainability Program partner HeroDevs" + "message": "Commercial support for versions past the Maintenance LTS phase is available through our OpenJS Ecosystem Sustainability Program partners" }, "eolChip": { "severity": { From 836dc70c6ad7bb1383758405d974a383cbc436a3 Mon Sep 17 00:00:00 2001 From: bmuenzenmeyer Date: Tue, 14 Oct 2025 10:20:31 -0400 Subject: [PATCH 2/2] add copy from marketing --- apps/site/pages/en/about/eol.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/apps/site/pages/en/about/eol.mdx b/apps/site/pages/en/about/eol.mdx index 695f5be6f7bc1..e2d2cea883c5c 100644 --- a/apps/site/pages/en/about/eol.mdx +++ b/apps/site/pages/en/about/eol.mdx @@ -37,10 +37,10 @@ When a version reaches End-Of-Life, it means that it will no longer receive upda ## Commercial Support -Despite the obvious downsides of using EOL releases, in practice, organizations face constraints that prevent immediate upgrades, such as legacy codebases, compliance requirements, or complex dependency chains. For users who cannot upgrade immediately but needs continued security support for End-Of-Life versions of Node.js, commercial support is available through the [OpenJS Ecosystem Sustainability Program](https://openjsf.org/blog/ecosystem-sustainability-program) partnership. +Despite the obvious downsides of using EOL releases, in practice, organizations face constraints that prevent immediate upgrades, such as legacy codebases, compliance requirements, or complex dependency chains. Through the [OpenJS Foundation Ecosystem Sustainability Program](https://openjsf.org/blog/ecosystem-sustainability-program), Node.js is supported by HeroDevs and NodeSource to provide commercial services for security fixes. -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://nodejs.org/esp/herodevs). +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. -Using EOL releases through NES should be viewed as a temporary solution—the goal should always be to upgrade to actively supported versions. +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. -Node.js also partners with NodeSource... `` +Using EOL releases through commercial support should be viewed as a temporary solution—the goal should always be to upgrade to actively supported versions.