unraid · elibosley · May 25, 2026 · May 23, 2026 · May 23, 2026 · May 23, 2026
diff --git a/babel.config.js b/babel.config.js
diff --git a/docs/contribute/linear-release-note-template.mdx b/docs/contribute/linear-release-note-template.mdx
@@ -0,0 +1,149 @@
+---
+sidebar_position: 2
+sidebar_label: Linear release note template
+---
+
+# Linear release note template
+
+Use this template when asking a Linear agent to draft Unraid OS release notes from a release project, milestone, or issue list.
+
+## Linear agent prompt
+
+Copy this prompt into Linear, then replace the bracketed values before running it.
+
+```markdown
+Draft Unraid OS release notes for [VERSION] using the linked Linear issues, pull requests, package diff, and security notes.
+
+Release context:
+- Version: [VERSION]
+- Release date: [YYYY-MM-DD]
+- Previous release: [PREVIOUS_VERSION]
+- Release type: [stable / bugfix / security / beta / release candidate]
+- Audience: Unraid OS users upgrading from [PREVIOUS_VERSION]
+- Source scope: [Linear project, milestone, label, or issue list]
+
+Output only the final release note Markdown. Do not include process notes, issue IDs, internal-only implementation details, or unsupported claims.
+
+Follow this structure:
+
+# Version [VERSION] [YYYY-MM-DD]
+
+[One short summary paragraph. Mention the most important user-facing themes: security, kernel, Docker, storage, WebGUI, virtualization, licensing, hardware support, API, or package updates.]
+
+[Optional recommendation sentence for security or important bugfix releases.]
+
+## Upgrading
+
+For step-by-step instructions, see [Updating Unraid](/unraid-os/updating-unraid/). Questions about your [license](/unraid-os/troubleshooting/licensing-faq/)?
+
+### Known issues
+
+[List release-specific known issues. If there are no new release-specific known issues, refer to the previous relevant release notes.]
+
+### Notes
+
+[Optional operational notes that are important but not bugs, warnings, or rollback blockers.]
+
+### Rolling back
+
+[List rollback warnings and compatibility limits. Include prior-release links when users need to read earlier rollback notes.]
+
+## BREAKING CHANGES
+
+[Include only when the release changes behavior, configuration, compatibility, data format, upgrade safety, rollback safety, or user workflows in a way users must act on.]
+
+## Changes vs. [PREVIOUS_VERSION_LINK_TEXT]([PREVIOUS_VERSION_LINK])
+
+### Security
+
+- Security: [User-facing security fix, CVE coverage, or hardening change.]
+
+### Containers / Docker
+
+- New: [New Docker or container capability.]
+- Improvement: [Improved Docker or container behavior.]
+- Fix: [Corrected Docker or container issue.]
+
+### Storage
+
+- New: [New storage capability.]
+- Improvement: [Improved storage behavior.]
+- Fix: [Corrected storage issue.]
+
+### WebGUI / System
+
+- New: [New WebGUI or system capability.]
+- Improvement: [Improved WebGUI or system behavior.]
+- Fix: [Corrected WebGUI or system issue.]
+
+### File Manager
+
+- Improvement: [Improved File Manager behavior.]
+- Fix: [Corrected File Manager issue.]
+
+### Networking / Hardware
+
+- New: [New networking or hardware support.]
+- Improvement: [Improved networking or hardware behavior.]
+- Fix: [Corrected networking or hardware issue.]
+
+### Virtualization
+
+- New: [New VM capability.]
+- Improvement: [Improved VM behavior.]
+- Fix: [Corrected VM issue.]
+
+### Unraid API
+
+- Update Unraid API to dynamix.unraid.net [VERSION] - [see changes](https://github.com/unraid/api/releases).
+- Fix: [Corrected API issue.]
+
+### Linux kernel
+
+- Linux kernel: update to `[KERNEL_VERSION]-Unraid`.
+- Security: [Kernel CVE coverage, when applicable.]
+
+### Base distro updates
+
+#### Removed packages ([COUNT])
+
+- [package]: version [VERSION] removed
+
+#### Downgraded packages ([COUNT])
+
+- [package]: version [OLD_VERSION] -> [NEW_VERSION]
+
+#### Added packages ([COUNT])
+
+- [package]: version [VERSION]
+
+#### Updated packages ([COUNT])
+
+- [package]: version [OLD_VERSION] -> [NEW_VERSION] [(CVE list, when applicable)]
+```
+
+## Drafting rules
+
+- Lead with user impact. Convert engineering notes into what changed for users, administrators, or upgrade safety.
+- Keep bullets concise and factual. Do not include internal project names, issue IDs, branch names, commit hashes, or implementation details unless they matter to users.
+- Use the prefixes `New:`, `Improvement:`, `Fix:`, and `Security:` consistently in change sections.
+- Group related items under the most specific heading. Use `WebGUI / System` for broad UI, settings, system-service, licensing-state, and notification changes.
+- Include a `BREAKING CHANGES` section only when users must change behavior or when rollback, compatibility, networking, storage, data, or configuration behavior changes.
+- Do not invent CVEs, affected packages, package versions, rollback warnings, known issues, or upgrade recommendations. If the source material is unclear, write `[NEEDS CONFIRMATION: ...]`.
+- Preserve public source links when they help users verify details, such as upstream release notes, user reports, or related docs.
+- Prefer docs links in this format: `/unraid-os/release-notes/[VERSION]/`.
+- Use **bold** for UI labels and **_bold italics_** for navigation paths, such as **_Settings → Disk Settings_**.
+- Use inline code for package names, commands, config keys, paths, versions, kernel config symbols, and error strings.
+- Remove unused optional sections before publishing.
+
+## Release-note checklist
+
+Before publishing, confirm that:
+
+- The heading is `# Version [VERSION] [YYYY-MM-DD]`.
+- The summary mentions the most important changes without repeating every section.
+- Upgrade, known issue, and rollback notes are accurate for this release.
+- Security claims match confirmed advisories or package changelogs.
+- Package counts match the package lists.
+- Previous-release links point to the correct version.
+- Optional sections with placeholders have been removed.
diff --git a/docs/unraid-connect/overview-and-setup.mdx b/docs/unraid-connect/overview-and-setup.mdx
@@ -115,7 +115,7 @@ When you click **Details** on a server, you will see:
 
 :::tip
 
-For full remote administration, prefer the official [%%Tailscale|tailscale%% integration](../unraid-os/system-administration/secure-your-server/tailscale.mdx). It gives you private remote access to the %%WebGUI|web-gui%% and services without exposing them to the public internet.
+For full remote administration, prefer the official [Tailscale integration](../unraid-os/system-administration/secure-your-server/tailscale.mdx). It gives you private remote access to the %%WebGUI|web-gui%% and services without exposing them to the public internet.
 
 :::
 

diff --git a/docs/unraid-connect/remote-access.mdx b/docs/unraid-connect/remote-access.mdx
@@ -5,11 +5,11 @@ sidebar_label: Remote access
 
 # Remote access
 
-This page covers **Unraid Connect Remote Access**, which publishes your %%WebGUI|web-gui%% to the internet by using either %%UPnP|upnp%% or a manual port forwarding rule on your router. If you want full remote management without exposing the %%WebGUI|web-gui%% to WAN traffic, prefer the official [%%Tailscale|tailscale%% integration](../unraid-os/system-administration/secure-your-server/tailscale.mdx). For more advanced needs, such as connecting to Docker containers or accessing network drives, a %%VPN Tunnel|vpn-tunnel%% remains the recommended solution.
+This page covers **Unraid Connect Remote Access**, which publishes your %%WebGUI|web-gui%% to the internet by using either %%UPnP|upnp%% or a manual port forwarding rule on your router. If you want full remote management without exposing the %%WebGUI|web-gui%% to WAN traffic, prefer the official [Tailscale integration](../unraid-os/system-administration/secure-your-server/tailscale.mdx). For more advanced needs, such as connecting to Docker containers or accessing network drives, a %%VPN Tunnel|vpn-tunnel%% remains the recommended solution.
 
 :::important[Security reminder]
 
-Before enabling remote access, ensure your root password is strong and unique. Update it on the **Users** page if required. Additionally, keep your Unraid OS updated to the latest version to protect against security vulnerabilities. [Learn more about updating Unraid here](../unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx).
+Before enabling remote access, ensure your root password is strong and unique. Update it on the **Users** page if required. Additionally, keep your Unraid OS updated to the latest version to protect against security vulnerabilities. [Learn more about updating Unraid here](/unraid-os/updating-unraid/).
 
 :::
 
@@ -27,7 +27,7 @@ Remote access through Unraid Connect provides:
 
 :::tip[Preferred approach]
 
-For most users, the official [%%Tailscale|tailscale%% integration](../unraid-os/system-administration/secure-your-server/tailscale.mdx) is the better choice for remote administration because it avoids exposing the %%WebGUI|web-gui%% to the public internet. Use Unraid Connect Remote Access only when you specifically need browser access to the public-facing %%WebGUI|web-gui%% URL.
+For most users, the official [Tailscale integration](../unraid-os/system-administration/secure-your-server/tailscale.mdx) is the better choice for remote administration because it avoids exposing the %%WebGUI|web-gui%% to the public internet. Use Unraid Connect Remote Access only when you specifically need browser access to the public-facing %%WebGUI|web-gui%% URL.
 
 :::
 
@@ -56,7 +56,7 @@ In current Unraid 7.2.x releases, the Unraid API settings page exposes these rem
 
 When remote access is set to **Always**, your %%WebGUI|web-gui%% is continuously reachable from the internet on the configured WAN port. Both **Static** and **UPnP** remote access publish the %%WebGUI|web-gui%% to WAN traffic. Use a strong root password, keep Unraid OS updated, and disable remote access when you do not need it.
 
-Dynamic, on-demand remote access is not currently exposed in the Unraid API settings page. If you need remote management without keeping the %%WebGUI|web-gui%% exposed through port forwarding, prefer [%%Tailscale|tailscale%%](../unraid-os/system-administration/secure-your-server/tailscale.mdx) or another %%VPN Tunnel|vpn-tunnel%%.
+Dynamic, on-demand remote access is not currently exposed in the Unraid API settings page. If you need remote management without keeping the %%WebGUI|web-gui%% exposed through port forwarding, prefer [Tailscale](../unraid-os/system-administration/secure-your-server/tailscale.mdx) or another %%VPN Tunnel|vpn-tunnel%%.
 
 ## Enable remote access
 

diff --git a/docs/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdx b/docs/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdx
@@ -15,7 +15,7 @@ For typical USB installs, that means a quality USB flash drive; licensing depend
 
 :::
 
-## Automated install method
+## Automated install method {/* #automated-install-method */}
 
 The automated installation method is the best way to set up Unraid OS. It simplifies the process, reduces errors, and ensures your USB flash drive is ready for most hardware configurations. This method offers the quickest and most reliable path to a successful installation for most users.
 
@@ -38,17 +38,15 @@ The automated installation method is the best way to set up Unraid OS. It simpli
 6. **Boot into Unraid OS:**
    Save your BIOS configuration, then exit to boot into Unraid OS.
 
-## Manual install method
+## Manual install method {/* #manual-install-method */}
 
 The manual installation method is designed for situations where the USB Flash Creator tool is either unavailable or incompatible with your hardware. This approach provides complete control over the formatting and setup process, making it ideal for advanced users or for troubleshooting specific issues with a USB device.
 
-<a id="choosing-a-usb-flash-drive"></a>
-
-### Choosing a boot device
+### Choosing a boot device {/* #choosing-a-usb-flash-drive */}
 
 <FlashDriveGuidance />
 
-### Prepare your USB device
+### Prepare your USB device {/* #prepare-your-usb-device */}
 
 1. Plug in the USB drive you are preparing as the boot device.
 2. Format it to FAT32 (**not** ex-FAT or NTFS).

diff --git a/...raid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx b/...raid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx
@@ -77,9 +77,7 @@ A single power outage or incomplete write can sometimes cause minor corruption,
 
 There are two ways to replace your Unraid boot device: the recommended [USB Flash Creator](https://unraid.net/download) tool for Windows or macOS (for USB boot media), or the manual method for advanced users. **Always back up your boot device before starting.**
 
-<a id="backing-up-your-flash-device"></a>
-
-### Backing up your boot device
+### Backing up your boot device {/* #backing-up-your-flash-device */}
 
 <Tabs>
   <TabItem value="webgui" label="Using the WebGUI" default>

diff --git a/docs/unraid-os/system-administration/secure-your-server/secure-your-boot-drive.mdx b/docs/unraid-os/system-administration/secure-your-server/secure-your-boot-drive.mdx
@@ -11,7 +11,7 @@ The boot device is essential to your Unraid server, as it stores all configurati
 
 <WebguiBootDeviceLabels />
 
-## Backups
+## Backups {/* #backups */}
 
 Having a recent backup of your boot device ensures you can quickly recover from hardware failures, accidental changes, or data corruption. Be sure to create backups in the following situations:
 

diff --git a/...raid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx b/...raid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx
@@ -25,7 +25,7 @@ There are three main methods to secure your outgoing communications:
 
 For most users, solutions like [Tailscale](./tailscale.mdx) or [WireGuard](./wireguard.mdx) are preferred for full-system security and privacy. Use Outgoing Proxy Manager when you only need to proxy Unraid's own HTTP requests.
 
-### Setting up a proxy server
+### Setting up a proxy server {/* #setting-up-a-proxy-server */}
 
 To set up a proxy server:
 
@@ -64,7 +64,7 @@ To monitor proxy traffic, go to the **Docker** tab on the proxy host system, sel
 
 For additional information about plugin development and compatibility, visit the [Plugins section of the documentation](../../using-unraid-to/customize-your-experience/plugins.mdx).
 
-## Tailscale exit nodes
+## Tailscale exit nodes {/* #tailscale-exit-nodes */}
 
 %%Tailscale|tailscale%% exit nodes offer a secure and modern way to route your Unraid server's outgoing traffic through another device on your %%Tailnet|tailnet%%. This setup provides the security of a %%VPN|vpn-tunnel%% while leveraging %%Tailscale|tailscale%%'s easy-to-use mesh networking, making it ideal for users who want encrypted outgoing traffic without the complexity of traditional %%VPN|vpn-tunnel%%s.
 
@@ -102,7 +102,7 @@ You can also set up a Docker container to function as a %%Tailscale|tailscale%%
 3. **Approve the exit node** in your %%Tailscale|tailscale%% admin console.
 4. **Select the container** as an exit node for your other devices on the %%Tailnet|tailnet%%.
 
-## Outgoing VPN connections
+## Outgoing VPN connections {/* #outgoing-vpn-connections */}
 
 Unraid supports outgoing WireGuard VPN connections to commercial providers, allowing you to route Docker containers or your entire server’s traffic through a secure tunnel. This is useful for privacy, bypassing geo-restrictions, or securing outbound data. For community insights and troubleshooting, see the [WireGuard VPN tunneled access forum thread](https://forums.unraid.net/topic/84316-wireguard-vpn-tunneled-access/).
 

diff --git a/docs/unraid-os/system-administration/secure-your-server/securing-your-data.mdx b/docs/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
@@ -24,7 +24,7 @@ Encryption increases your data security, but can complicate recovery from hardwa
 
 </details>
 
-## How to encrypt a drive in Unraid
+## How to encrypt a drive in Unraid {/* #how-to-encrypt-a-drive-in-unraid */}
 
 :::warning
 

diff --git a/docs/unraid-os/system-administration/secure-your-server/user-management.mdx b/docs/unraid-os/system-administration/secure-your-server/user-management.mdx
@@ -62,7 +62,7 @@ Share users...
 
 ---
 
-## Add users
+## Add users {/* #add-users */}
 
 To connect to shared files on Unraid from another device, you'll need a username and password. These credentials are separate from the ones you might use for specific applications running in containers, which have their own login information.
 
@@ -124,7 +124,7 @@ To modify a user account:
 
 ---
 
-## Reset your password
+## Reset your password {/* #reset-your-password */}
 
 If you've forgotten your %%root|root-user%% password, don't worry! Here are two simple methods to regain access to your Unraid server. You'll need physical access to your **[boot device](../../system-administration/maintain-and-update/changing-the-flash-device.mdx)** (for example the USB drive) and another computer.
 

diff --git a/docs/unraid-os/system-administration/secure-your-server/wireguard.mdx b/docs/unraid-os/system-administration/secure-your-server/wireguard.mdx
@@ -178,7 +178,7 @@ This setup is especially important for **Remote tunneled access** mode, where th
 
 :::
 
-### Complex networks
+### Complex networks {/* #complex-networks */}
 
 For most users, the default **Use NAT** setting works out of the box and allows access to Unraid and most LAN devices. However, if you use Docker containers with custom IPs or %%VM|vm%%s with strict networking requirements:
 

diff --git a/docs/unraid-os/troubleshooting/common-issues/data-recovery.mdx b/docs/unraid-os/troubleshooting/common-issues/data-recovery.mdx
@@ -50,7 +50,7 @@ With Unraid 7.0 and up, enable [Unraid Connect](../../../unraid-connect/overview
 
 ---
 
-## Repair file systems
+## Repair file systems {/* #repair-file-systems */}
 
 :::caution
 
@@ -142,7 +142,7 @@ This section covers how to diagnose and repair file system corruption on data dr
   </TabItem>
 </Tabs>
 
-### After the test and repair
+### After the test and repair {/* #after-the-test-and-repair */}
 
 If you used %%Maintenance Mode|maintenance-mode%%, stop the array and restart it in normal mode to resume operations.
 

diff --git a/docs/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx b/docs/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx
@@ -137,7 +137,7 @@ This script only performs read-only operations and won't modify any data on your
 
 ---
 
-## Persistent logs (syslog server)
+## Persistent logs (syslog server) {/* #persistent-logs-syslog-server */}
 
 Persistent logs are essential for keeping a record of system events between reboots. Unlike standard logs that reset when the system restarts, persistent logs use Unraid's built-in %%syslog server|syslog-server%% to ensure you can diagnose crashes or intermittent issues that arise over time.
-Original file line number
+Diff line change
@@ Expand Up / @@ -115,7 +115,7 @@ When you click **Details** on a server, you will see: @@
     :::tip
-    For full remote administration, prefer the official [%%Tailscale|tailscale%% integration](../unraid-os/system-administration/secure-your-server/tailscale.mdx). It gives you private remote access to the %%WebGUI|web-gui%% and services without exposing them to the public internet.
+    For full remote administration, prefer the official [Tailscale integration](../unraid-os/system-administration/secure-your-server/tailscale.mdx). It gives you private remote access to the %%WebGUI|web-gui%% and services without exposing them to the public internet.
     :::
@@ Expand Down @@