docs(eol): clarify release support status

elibosley · elibosley · commit a99a04bd4395 · 2026-05-13T17:22:30.000-04:00
- Purpose: add the EOL support-policy changes to the release archive docs branch.

- Before: the version archive grouped releases by stable, previous, and legacy without clearly explaining superseded builds or EOL support boundaries.

- Problem: users could confuse archived or older patch builds with currently supported update targets.

- Now: the docs define supported minor series, superseded patch builds, and EOL releases across the archive, licensing FAQ, and release-types guide.

- Implementation: simplify the VersionsTable status filters, mark current and previous series support status dynamically, and update the 7.3.0 release notes to stable-release wording.
diff --git a/docs/unraid-os/download_list.mdx b/docs/unraid-os/download_list.mdx
@@ -3,12 +3,14 @@ sidebar_position: 9
 title: Version Archive
 ---
 
-import {VersionsTable} from '@site/src/components/VersionsTable';
+import { VersionsTable } from "@site/src/components/VersionsTable";
 
 # Version Archive
 
 Use this archive to find release notes and download links for Unraid OS versions. To update an existing server, use the built-in updater; see the [standard update process](./updating-unraid/index.mdx#standard-update-process) for steps. To create a new boot device, use the [Unraid USB Creator](https://unraid.net/download).
 
-If you are deciding which release to install, start with [Unraid OS release types](./updating-unraid/release-types.mdx).
+The archive groups releases by support status. Only the latest patch or pre-release build in a supported minor series receives updates as appropriate; older builds in the same series are superseded. Releases marked **EOL** are not supported and no longer include updates.
+
+If you are deciding which release to install, start with [Unraid OS release types](./updating-unraid/release-types.mdx). For license eligibility details, see the [Licensing FAQ](./troubleshooting/licensing-faq.mdx#no-extension).
 
 <VersionsTable />
diff --git a/docs/unraid-os/troubleshooting/licensing-faq.mdx b/docs/unraid-os/troubleshooting/licensing-faq.mdx
@@ -47,7 +47,7 @@ For bulk OEM/reseller pricing (10 licenses or more), [contact Unraid](https://un
 
 ### How do I upgrade my Unraid license? {/* #upgrade-license */}
 
-You can upgrade your license at any time from within the %%WebGUI|web-gui%% (***Tools → Registration***) or [via the account portal](https://account.unraid.net/keys) (by clicking **••• More** and selecting **Upgrade Key**).
+You can upgrade your license at any time from within the %%WebGUI|web-gui%% (**_Tools → Registration_**) or [via the account portal](https://account.unraid.net/keys) (by clicking **••• More** and selecting **Upgrade Key**).
 
 <div style={{ display: "flex", justifyContent: "center", margin: "20px 0" }}>
 
@@ -66,15 +66,18 @@ You can upgrade your license at any time from within the %%WebGUI|web-gui%% (***
 
 **Annual extension fee** (Starter & Unleashed only): $36 USD
 
-<sup>1</sup> Attached storage devices include all devices present before array start, except one eMMC device and one USB device.\
-<sup>2</sup> "Unlimited" means you are not limited by the license, but by hardware and OS constraints. Additional storage devices can be used for %%VMs|vm%%, unassigned devices, or other Unraid features.\*
+<sup>1</sup> Attached storage devices include all devices present before array
+start, except one eMMC device and one USB device.\
+<sup>2</sup> "Unlimited" means you are not limited by the license, but by
+hardware and OS constraints. Additional storage devices can be used for
+%%VMs|vm%%, unassigned devices, or other Unraid features.\*
 
 ### How do I manually install my license keyfile to my boot device? {/* #manual-keyfile-install */}
 
 #### Install via WebGUI download
 
 1. Navigate to [account.unraid.net/keys](https://account.unraid.net/keys), select **View options** next to your key, then click **Copy Key URL**.
-2. Navigate to your server's ***Tools → Registration***.
+2. Navigate to your server's **_Tools → Registration_**.
 3. Scroll to the bottom of the Registration page, to the **Install Key** section.
 4. Paste the URL into the **Key file URL** field, and click **Install**.
 
@@ -88,16 +91,16 @@ You can upgrade your license at any time from within the %%WebGUI|web-gui%% (***
 
 This does not apply if you have configured internal boot.
 
-1. Ensure you have a recent backup of your USB drive. Use [Unraid Connect](../../unraid-connect/overview-and-setup.mdx) (recommended) or the local backup option at ***Main → Boot Device → Boot Device Backup*** (on releases before 7.3.0, use ***Main → Flash device → FLASH BACKUP***).
+1. Ensure you have a recent backup of your USB drive. Use [Unraid Connect](../../unraid-connect/overview-and-setup.mdx) (recommended) or the local backup option at **_Main → Boot Device → Boot Device Backup_** (on releases before 7.3.0, use **_Main → Flash device → FLASH BACKUP_**).
 2. Shut down your Unraid server and remove the USB boot device.
 3. Insert the USB drive into another computer.
 4. Open the USB drive and copy your `.key` file into the `/config` folder.
-   *Make sure this is the only `.key` file present - delete any others.*
+   _Make sure this is the only `.key` file present - delete any others._
 5. Safely eject the USB drive, reinstall it in your server, and reboot.
 
 ### How can I determine my registration type? {/* #registration-type */}
 
-Navigate to ***Tools → Registration*** in the %%WebGUI|web-gui%%. Here, you can find your current license type and registration details.
+Navigate to **_Tools → Registration_** in the %%WebGUI|web-gui%%. Here, you can find your current license type and registration details.
 
 For internal boot questions, see the [Internal Boot FAQ (7.3+)](../getting-started/set-up-unraid/internal-boot-faq.mdx).
 For TPM-based licensing questions, see the [TPM Licensing FAQ (7.3+)](tpm-licensing-faq.mdx).
@@ -120,16 +123,23 @@ You continue to own your license even if you stop paying for updates.
 
 - You keep your license and can use your current version of Unraid OS indefinitely.
 - You won't receive new feature updates or major version upgrades.
-- You remain eligible for patch releases and security updates within the same minor version (e.g., 7.1.x if your license lapsed at 7.1.0).
-- Once a new minor version is released (e.g., 7.2.0), only security patches are provided for the previous minor version.
-- When a version reaches end-of-life (EOL), no further updates are provided.
+- You remain eligible for supported patch releases within the same minor series that your license allows, such as `7.1.x` if your license lapsed at `7.1.0`.
+- Unraid supports two public minor series at a time: the current public minor series and the previous public minor series.
+- A public Beta or Release Candidate (RC) starts a public minor series for support-policy purposes, even though pre-releases are still intended for testing.
+- The latest patch or pre-release build in the current public minor series is supported for bug fixes and security updates as appropriate.
+- The latest patch in the previous public minor series is supported for security updates as appropriate.
+- Older patch builds in a supported minor series are superseded by the latest build in that series.
+- Older minor series are end-of-life (EOL). EOL releases are not supported and no longer include updates.
 - You can pay the extension fee at any time to regain access to the latest updates.
 
+For a release-by-release view of support status, see the [Version Archive](../download_list.mdx). For more detail about Stable, Beta, and RC releases, see [Unraid OS release types](../updating-unraid/release-types.mdx).
+
 ### What happens with pre-releases (Beta/RC versions)? {/* #pre-release-policy */}
 
 - Pre-release (Beta and Release Candidate) versions are for testing and may contain bugs.
 - Only install pre-releases on non-production systems.
-- Support for pre-releases ends when the stable version is released.
+- A public pre-release counts as the current public minor series when determining which minor series are supported.
+- Support for a specific pre-release build ends when it is superseded by a newer pre-release or the corresponding stable release.
 - Your license must be eligible for OS updates on the stable release date to receive the stable version.
 - If your license expires before the stable release, you must extend your license to upgrade or roll back to a supported stable version.
 - Your license remains valid after expiration; you only need an active license for new updates.
@@ -150,8 +160,11 @@ Here are the current limits:
 
 </div>
 
-<sup>1</sup> Attached storage devices include all devices present before %%array|array%% start, except one eMMC device and one USB device.\
-<sup>2</sup> "Unlimited" means you are not limited by the license, but by hardware and OS constraints. Additional storage devices can be used for %%VMs|vm%%, unassigned devices, or other Unraid features.\*
+<sup>1</sup> Attached storage devices include all devices present before
+%%array|array%% start, except one eMMC device and one USB device.\
+<sup>2</sup> "Unlimited" means you are not limited by the license, but by
+hardware and OS constraints. Additional storage devices can be used for
+%%VMs|vm%%, unassigned devices, or other Unraid features.\*
 
 ---
 
@@ -166,7 +179,7 @@ To transfer your license:
 1. Prepare new, high-quality [boot media](../getting-started/set-up-unraid/create-your-bootable-media.mdx) (for example a USB flash drive).
 2. Install Unraid OS on the new device using the USB Flash Creator or a manual method.
 3. Boot your server with the new boot device.
-4. Go to ***Tools → Registration*** in the %%WebGUI|web-gui%%.
+4. Go to **_Tools → Registration_** in the %%WebGUI|web-gui%%.
 5. Click **Replace Key** and follow the prompts to transfer your license to the new device.
 
 The first transfer can be done at any time, while subsequent transfers are allowed once every 12 months using the automated system. If you need to transfer your license again before the 12-month period, contact Unraid support with your old and new USB %%GUID|guid%%s for manual assistance.
diff --git a/docs/unraid-os/updating-unraid/release-types.mdx b/docs/unraid-os/updating-unraid/release-types.mdx
@@ -11,12 +11,27 @@ For most servers, use the latest **Stable** release. Use **Beta** or **Release C
 
 ## Release types at a glance
 
-| Release type | Example version | Best for | What to expect |
-| --- | --- | --- | --- |
-| **Stable** | `7.2.0`, then `7.2.1`, `7.2.2`, and later patches | Production servers | General availability release recommended for normal use. A stable series often begins with a `.0` minor release, then receives patch releases with fixes and compatibility updates. |
-| **Release Candidate (RC)** | `7.3.0-rc.1` | Final validation on test systems | A pre-release that is expected to be close to stable, but may still include unresolved issues or last-minute changes. |
-| **Beta** | `7.3.0-beta.2` | Early testing and feedback | A pre-release used to test new features, platform changes, fixes, and upgrade paths before the release is ready for stable use. |
-| **Withdrawn pre-release** | Varies | Moving off an unavailable test build | A beta or RC that is no longer enabled for regular use. Update to the latest stable release unless the release notes say otherwise. |
+| Release type               | Example version                                   | Best for                             | What to expect                                                                                                                                                                      |
+| -------------------------- | ------------------------------------------------- | ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Stable**                 | `7.2.0`, then `7.2.1`, `7.2.2`, and later patches | Production servers                   | General availability release recommended for normal use. A stable series often begins with a `.0` minor release, then receives patch releases with fixes and compatibility updates. |
+| **Release Candidate (RC)** | `7.3.0-rc.1`                                      | Final validation on test systems     | A pre-release that is expected to be close to stable, but may still include unresolved issues or last-minute changes.                                                               |
+| **Beta**                   | `7.3.0-beta.2`                                    | Early testing and feedback           | A pre-release used to test new features, platform changes, fixes, and upgrade paths before the release is ready for stable use.                                                     |
+| **Withdrawn pre-release**  | Varies                                            | Moving off an unavailable test build | A beta or RC that is no longer enabled for regular use. Update to the latest stable release unless the release notes say otherwise.                                                 |
+
+## Supported minor series and EOL
+
+Unraid supports two public minor series at a time:
+
+- The **current public minor series**, such as `7.3.x` once any `7.3` beta, RC, or stable release is public.
+- The **previous public minor series**, such as `7.2.x` while `7.3.x` is the current public series.
+
+A public beta or RC counts as a public minor series for support-policy purposes. This does not mean beta or RC releases are recommended for production use; it only means the support window moves forward when the next minor series becomes public.
+
+Within a supported minor series, use the latest available patch or pre-release build for that series. Older patch builds in the same series are superseded and remain available only for archive, rollback, and release-note reference.
+
+Older minor series are **End of Life (EOL)**. EOL releases are not supported and no longer include bug fixes or security updates.
+
+To check the current status of a release, see the [Version Archive](../download_list.mdx).
 
 ## Stable releases
 
@@ -61,7 +76,7 @@ RC releases are useful when:
 
 ## Release branches and the Update OS tool
 
-In the WebGUI, open ***Tools -> Update OS*** or use **Check for Update** from the top-right menu.
+In the WebGUI, open **_Tools -> Update OS_** or use **Check for Update** from the top-right menu.
 
 The Update OS tool shows updates for the release branch your server is already using. To change release branches, open the top-right account menu and choose **Manage Unraid.net Account** to manage the server in the [Unraid account app](../../unraid-account/server-management.mdx). You cannot switch release branches directly from inside the OS.
 
@@ -77,7 +92,8 @@ Your license remains valid even if your update eligibility expires. Update eligi
 For pre-releases:
 
 - Beta and RC versions are for testing and may contain bugs.
-- Support for a pre-release ends when the corresponding stable version is released.
+- Public beta and RC versions count when identifying the current public minor series.
+- Support for a specific pre-release build ends when it is superseded by a newer pre-release or the corresponding stable release.
 - Your license must be eligible for OS updates on the stable release date to receive that stable version.
 - If your update eligibility expires before the stable release, you must extend your license to upgrade to that stable version or roll back to a supported stable version that your license allows.
 
@@ -100,7 +116,7 @@ Good feedback helps turn beta and RC builds into better stable releases and help
 
 - The exact Unraid OS version.
 - Whether the issue started after updating.
-- Diagnostics from ***Tools -> Diagnostics***.
+- Diagnostics from **_Tools -> Diagnostics_**.
 - Steps to reproduce the issue.
 - Any relevant plugin, Docker, VM, network, or storage configuration details.
 
diff --git a/src/components/VersionsTable.tsx b/src/components/VersionsTable.tsx
