Prefer EoL capitalization of EOL

MattIPv4 · MattIPv4 · commit 1a673840c733 · 2026-04-16T23:05:34.000+01:00
diff --git a/apps/site/components/EOL/EOLReleaseTable/index.tsx b/apps/site/components/EOL/EOLReleaseTable/index.tsx
@@ -14,7 +14,7 @@ const EOLReleaseTable: FC = async () => {
   const releaseData = await provideReleaseData();
   const vulnerabilities = await provideVulnerabilities();
 
-  const eolReleases = releaseData.filter(release => release.status === 'EOL');
+  const eolReleases = releaseData.filter(release => release.status === 'EoL');
 
   const t = await getTranslations();
 
diff --git a/apps/site/components/withReleaseAlertBox.tsx b/apps/site/components/withReleaseAlertBox.tsx
@@ -14,7 +14,7 @@ const WithReleaseAlertBox: FC<WithReleaseAlertBoxProps> = ({ status }) => {
   const t = useTranslations();
 
   switch (status) {
-    case 'EOL':
+    case 'EoL':
       return (
         <AlertBox
           title={t('components.common.alertBox.warning')}
diff --git a/apps/site/next-data/generators/__tests__/releaseData.test.mjs b/apps/site/next-data/generators/__tests__/releaseData.test.mjs
@@ -19,7 +19,7 @@ describe('generateReleaseData', () => {
     return generateReleaseData();
   };
 
-  it('returns EOL when release is on or past EOL date', async t => {
+  it('returns EoL when release is on or past EoL date', async t => {
     const result = await runWithNodevuData(t, '2024-10-18', {
       14: {
         releases: {
@@ -43,10 +43,10 @@ describe('generateReleaseData', () => {
       },
     });
 
-    assert.equal(result[0]?.status, 'EOL');
+    assert.equal(result[0]?.status, 'EoL');
   });
 
-  it('returns Current when release is not EOL and latest is not LTS', async t => {
+  it('returns Current when release is not EoL and latest is not LTS', async t => {
     const result = await runWithNodevuData(t, '2026-04-14', {
       20: {
         releases: {
@@ -74,7 +74,7 @@ describe('generateReleaseData', () => {
     assert.equal(result[0]?.status, 'Current');
   });
 
-  it('returns LTS when release is not EOL and latest is flagged as LTS', async t => {
+  it('returns LTS when release is not EoL and latest is flagged as LTS', async t => {
     const result = await runWithNodevuData(t, '2026-04-14', {
       22: {
         releases: {
@@ -102,7 +102,7 @@ describe('generateReleaseData', () => {
     assert.equal(result[0]?.status, 'LTS');
   });
 
-  it('returns Current when release is not EOL and LTS date has passed but latest is not LTS', async t => {
+  it('returns Current when release is not EoL and LTS date has passed but latest is not LTS', async t => {
     const result = await runWithNodevuData(t, '2026-04-14', {
       24: {
         releases: {
diff --git a/apps/site/next-data/generators/releaseData.mjs b/apps/site/next-data/generators/releaseData.mjs
@@ -7,7 +7,7 @@ const getNodeReleaseStatus = (latest, eol) => {
   const now = new Date();
 
   if (eol && now >= new Date(eol)) {
-    return 'EOL';
+    return 'EoL';
   }
 
   if (latest.lts.isLts) {
diff --git a/apps/site/next.constants.mjs b/apps/site/next.constants.mjs
@@ -210,7 +210,7 @@ export const SEVERITY_KIND_MAP = {
  * @type {Record<import('./types/releases').NodeReleaseStatus, import('@node-core/ui-components/Common/Badge').BadgeKind>}
  */
 export const STATUS_KIND_MAP = {
-  EOL: 'warning',
+  EoL: 'warning',
   LTS: 'info',
   Current: 'default',
 };
diff --git a/apps/site/pages/en/about/eol.mdx b/apps/site/pages/en/about/eol.mdx
@@ -1,10 +1,10 @@
 ---
 title: End-Of-Life
 layout: about
-description: Understand Node.js End-of-Life, what it means for security, tooling, and compliance, plus EOL version details and commercial support options.
+description: Understand Node.js End-of-Life, what it means for security, tooling, and compliance, plus EoL version details and commercial support options.
 ---
 
-# End-Of-Life (EOL)
+# End-Of-Life (EoL)
 
 ## Why and how Node.js releases reach End-Of-Life
 
@@ -16,29 +16,29 @@ Major versions of Node.js are released, patched, and designated End-Of-Life on a
   </Button>
   <span>or</span>
   <Button as="a" kind="warning" href="#commercial-support" className="flex-1">
-    <span>Get security support for EOL versions</span>
+    <span>Get security support for EoL versions</span>
   </Button>
 </div>
 
 [View the Node.js release schedule](/about/releases/).
 
-## What Happens When a Release Line Reaches EOL
+## What Happens When a Release Line Reaches EoL
 
 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.
 
-- **No more vulnerability fixes**: When new security releases reveal issues and patches in newer major lines, even if the same vulnerability affects EOL release lines, there will not be any new releases for them. Users still clinging on to EOL release lines and using affected code paths will be immediately vulnerable to attacks exploiting these disclosed vulnerabilities.
-- **Tool-chain breakage**: EOL releases may no longer dynamically link to newer versions of the shared libraries they depend on, blocking or breaking system updates.
-- **Ecosystem drift**: Many popular user-land packages drop support for EOL Node.js releases over time. When an application clings onto outdated packages, it may suffer from even more unfixed vulnerabilities and bugs, further drifting away from ecosystem norm.
+- **No more vulnerability fixes**: When new security releases reveal issues and patches in newer major lines, even if the same vulnerability affects EoL release lines, there will not be any new releases for them. Users still clinging on to EoL release lines and using affected code paths will be immediately vulnerable to attacks exploiting these disclosed vulnerabilities.
+- **Tool-chain breakage**: EoL releases may no longer dynamically link to newer versions of the shared libraries they depend on, blocking or breaking system updates.
+- **Ecosystem drift**: Many popular user-land packages drop support for EoL Node.js releases over time. When an application clings onto outdated packages, it may suffer from even more unfixed vulnerabilities and bugs, further drifting away from ecosystem norm.
 - **Compliance red flags**: Many industry audits forbid unmaintained runtimes.
 
-## EOL Versions
+## EoL Versions
 
 <EOLReleaseTable />
 
 ## 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. 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.
+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.
 
 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 commercial support should be viewed as a temporary solution—the goal should always be to upgrade to actively supported versions.
+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/pages/en/about/partners.mdx b/apps/site/pages/en/about/partners.mdx
@@ -29,13 +29,13 @@ Supporters are individuals and organizations that provide financial support thro
 
 ## Ecosystem Sustainability Program (ESP)
 
-Do you run a node.js version on End-of-Life (EOL)? The OpenJS Ecosystem Sustainability Program (ESP)
-is a program that helps organizations to maintain their Node.js applications on EOL versions.
+Do you run a node.js version on End-of-Life (EoL)? The OpenJS Ecosystem Sustainability Program (ESP)
+is a program that helps organizations to maintain their Node.js applications on EoL versions.
 The program provides access to security patches, compliance assistance, and technical support
 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 commercial support 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.
 
 <PartnersList size="large" category="esp" />
diff --git a/apps/site/pages/en/about/previous-releases.mdx b/apps/site/pages/en/about/previous-releases.mdx
@@ -43,7 +43,7 @@ Installation methods designated as “Official” must meet the following requir
 
 Community installation methods included on the self-service download page (located at /download) must also adhere to a minimum set of criteria:
 
-- **Version Support:** Must support all currently supported, non-End-of-Life (EOL) Node.js versions.
+- **Version Support:** Must support all currently supported, non-End-of-Life (EoL) Node.js versions.
 - **OS Compatibility:** Must function on at least one officially supported Operating System (OS).
 - **Broad OS Support:** Cannot be limited to a subset of OS distributions or versions.
   - For example, an installation method claiming compatibility with “Windows” must function on “Windows 10”, “Windows 11”, and all their editions (including server versions).
diff --git a/apps/site/pages/en/index.mdx b/apps/site/pages/en/index.mdx
@@ -24,7 +24,7 @@ layout: home
       <Button kind="secondary" className="!block" href="/about/eol">
         <span>Get security support</span>
         <br />
-        <small className="!text-xs">for EOL Node.js versions</small>
+        <small className="!text-xs">for EoL Node.js versions</small>
       </Button>
 
       <div className="flex justify-center ml:mt-3">
diff --git a/apps/site/types/releases.ts b/apps/site/types/releases.ts
@@ -1,4 +1,4 @@
-export type NodeReleaseStatus = 'LTS' | 'Current' | 'EOL';
+export type NodeReleaseStatus = 'LTS' | 'Current' | 'EoL';
 
 export type NodeReleaseSource = {
   major: number;
diff --git a/apps/site/util/download/constants.json b/apps/site/util/download/constants.json
@@ -213,5 +213,5 @@
     "bitness": ["64", "32"],
     "architecture": ["arm", "x86"]
   },
-  "statusOrder": ["Current", "LTS", "EOL"]
+  "statusOrder": ["Current", "LTS", "EoL"]
 }
diff --git a/docs/partners.md b/docs/partners.md
@@ -14,7 +14,7 @@ To add or remove a partner:
    - `href`: A URL linking to the partner’s website.
    - `categories`: An array of categories the partner belongs to. These are used to filter partners on the Partners and Downloads pages. Valid categories include:
      - `infrastructure`: Partners providing infrastructure for the Node.js project.
-     - `esp`: Partners offering support for EOL Node.js versions through the Ecosystem Sustainability Program (ESP).
+     - `esp`: Partners offering support for EoL Node.js versions through the Ecosystem Sustainability Program (ESP).
    - `weight`: A number representing the partner's visibility weight. This is used in the randomization algorithm — higher values increase the partner's likelihood of being shown.
 
 2. Add the partner's logo to the `packages/ui-components/icons/PartnersLogos/` directory.
diff --git a/docs/site-config.md b/docs/site-config.md
@@ -4,7 +4,7 @@
 
 It is imported via `apps/site/next.json.mjs` and exposed as a read-only API endpoint at `/site.json`.
 
-This endpoint is also consumed externally by the [doc-kit](https://github.com/nodejs/doc-kit) to display dynamic banners inside the API docs, for example security announcements or EOL notices, without requiring a doc-kit release.
+This endpoint is also consumed externally by the [doc-kit](https://github.com/nodejs/doc-kit) to display dynamic banners inside the API docs, for example security announcements or EoL notices, without requiring a doc-kit release.
 
 ## Structure
 
@@ -124,4 +124,4 @@ The response is `application/json` and is statically cached at build time. It re
 
 ### External consumers
 
-The [doc-kit](https://github.com/nodejs/doc-kit) fetches this endpoint asynchronously on page load to inject banners into the Node.js API documentation site. This allows publishing announcements (security releases, EOL notices, etc.) that appear in the API docs without requiring a doc-kit release or a rebuild of the static documentation.
+The [doc-kit](https://github.com/nodejs/doc-kit) fetches this endpoint asynchronously on page load to inject banners into the Node.js API documentation site. This allows publishing announcements (security releases, EoL notices, etc.) that appear in the API docs without requiring a doc-kit release or a rebuild of the static documentation.
diff --git a/packages/i18n/src/locales/en.json b/packages/i18n/src/locales/en.json
@@ -55,7 +55,7 @@
           "releases": "Node.js Releases",
           "security": "Security Reporting",
           "partners": "Partners & Supporters",
-          "eol": "End-of-Life (EOL)"
+          "eol": "End-of-Life (EoL)"
         }
       },
       "getInvolved": {
@@ -89,7 +89,7 @@
       "overview": "Overview",
       "minorVersions": "Minor versions",
       "releaseAnnouncement": "Release Announcement",
-      "unsupportedVersionWarning": "This version is out of maintenance. Please use a supported version. <link>Understand EOL support.</link>",
+      "unsupportedVersionWarning": "This version is out of maintenance. Please use a supported version. <link>Understand EoL support.</link>",
       "ltsVersionFeaturesNotice": "Want new features sooner? Get the <link>latest Node.js version</link> instead and try the latest improvements!"
     },
     "eolAlert": {
@@ -105,8 +105,8 @@
       }
     },
     "eolModal": {
-      "title": "Node.js v{version} ({codename}) has reached EOL",
-      "titleWithoutCodename": "Node.js v{version} has reached EOL",
+      "title": "Node.js v{version} ({codename}) has reached EoL",
+      "titleWithoutCodename": "Node.js v{version} has reached EoL",
       "vulnerabilitiesMessage": "There are {count}+ known security issues (CVEs) associated with this Node.js release. CVEs (Common Vulnerabilities and Exposures) are identifiers for publicly reported security flaws. Clicking a CVE link will take you to more technical details, such as how the vulnerability works.",
       "noVulnerabilitiesMessage": "There are currently no known CVEs (Common Vulnerabilities and Exposures) associated with this Node.js release. However, that doesn't mean it's completely secure—some vulnerabilities may not yet be discovered or publicly disclosed. If this release is outdated or unsupported, it's still a good idea to consider upgrading to ensure you benefit from the latest fixes and security improvements.",
       "blogLinkText": "Blog",
@@ -286,7 +286,7 @@
         }
       },
       "codeBox": {
-        "unsupportedVersionWarning": "This version is out of maintenance. Please use a currently supported version. <link>Understand EOL support.</link>",
+        "unsupportedVersionWarning": "This version is out of maintenance. Please use a currently supported version. <link>Understand EoL support.</link>",
         "ltsVersionFeaturesNotice": "Want new features sooner? Get the <link>latest Node.js version</link> instead and try the latest improvements!",
         "communityPlatformInfo": "Installation methods that involve community software are supported by the teams maintaining that software.",
         "externalSupportInfo": "If you encounter any issues please visit <link>{platform}'s website</link>",
diff --git a/packages/ui-components/src/Common/BaseButton/index.stories.tsx b/packages/ui-components/src/Common/BaseButton/index.stories.tsx
@@ -37,7 +37,7 @@ export const Secondary: Story = {
 export const Warning: Story = {
   args: {
     kind: 'warning',
-    children: 'Get security support for EOL versions ',
+    children: 'Get security support for EoL versions',
     disabled: false,
     size: 'default',
   },

Original file line number	Diff line number	Diff line change
`@@ -7,7 +7,7 @@ const getNodeReleaseStatus = (latest, eol) => {`
`7`	`7`	`const now = new Date();`
`8`	`8`
`9`	`9`	`if (eol && now >= new Date(eol)) {`
`10`		`- return 'EOL';`
	`10`	`+ return 'EoL';`
`11`	`11`	`}`
`12`	`12`
`13`	`13`	`if (latest.lts.isLts) {`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-export type NodeReleaseStatus = 'LTS' \| 'Current' \| 'EOL';`
	`1`	`+export type NodeReleaseStatus = 'LTS' \| 'Current' \| 'EoL';`
`2`	`2`
`3`	`3`	`export type NodeReleaseSource = {`
`4`	`4`	`major: number;`