feat: Update 7.3.0 rc.1 release notes#465
Merged
Merged
Conversation
- Purpose: publish the 7.3.0-rc.1 release-note draft from the current file changes. - Before: the page still presented the 7.3.0-beta.2 changelog structure and package inventory. - Why: users upgrading from 7.2.4 need the current 7.3.0 rc.1 feature and package summary. - What: rewrites the release notes around the rc.1 scope, beta.2 deltas, Docker/storage/WebGUI updates, and package versions. - How: updates docs/unraid-os/release-notes/7.3.0.md only, keeping validation focused on markdown checks.
Contributor
📝 WalkthroughWalkthroughThis pull request converts the 7.3.0 release notes from beta.2 to rc.1, changes the changelog baseline to 7.2.4, and reorganizes sections covering Security, Onboarding/internal-boot, Docker v29 migration details, Storage, WebGUI/System, Virtualization/Networking, platform package versions, and prerelease tester notes. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant WebGUI
participant DockerEngine
participant TemplateStore
participant Storage
User->>WebGUI: Initiate onboarding / upgrade
WebGUI->>Storage: Check internal-boot device & drivers
WebGUI-->>User: Show Array Offline / onboarding UI
WebGUI->>DockerEngine: Trigger container migration (v29)
DockerEngine->>TemplateStore: Lookup templates (case-sensitive)
TemplateStore-->>DockerEngine: Return template / optional fixed MAC
DockerEngine->>Storage: Persist migrated container metadata
DockerEngine-->>WebGUI: Report phantom-container status / live MACs
WebGUI-->>User: Display migration results and warnings
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (2)
docs/unraid-os/release-notes/7.3.0.md (2)
143-143: Link this API line item to the exact 4.32.3 release if available.Using the generic releases page makes auditing harder. A direct tag/release URL for
4.32.3would improve traceability.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/unraid-os/release-notes/7.3.0.md` at line 143, Update the `dynamix.unraid.net` 4.32.3 line so its link points to the specific 4.32.3 release tag/page instead of the generic releases page (replace the current https://github.com/unraid/api/releases URL with the exact release URL for 4.32.3); ensure the display text still reads "dynamix.unraid.net 4.32.3" and the link targets the precise 4.32.3 release for traceability.
69-70: Keep the bold “Important” note on one line for Markdown robustness.The emphasis marker is split across lines, which can be fragile across renderers/tooling. Prefer a single-line bold sentence.
Suggested edit
-**Important: Docker has been updated from v27 (in 7.2.4) to v29. This changes how MAC addresses are allocated to containers and randomizes them. -** +**Important: Docker has been updated from v27 (in 7.2.4) to v29. This changes how MAC addresses are allocated to containers and randomizes them.**🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/unraid-os/release-notes/7.3.0.md` around lines 69 - 70, The bold "Important" sentence is split across lines which can break some Markdown renderers; edit the release note text so the entire sentence "**Important: Docker has been updated from v27 (in 7.2.4) to v29. This changes how MAC addresses are allocated to containers and randomizes them.**" appears on a single line (no hard line breaks inside the bold markers) and leave surrounding blank lines intact to preserve paragraph separation.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/unraid-os/release-notes/7.3.0.md`:
- Line 36: The release note mentions "libpng" CVE remediation but the base
distro package list doesn't show a libpng version; either add an explicit libpng
package/version entry in the base-distro section (so readers can verify the fix)
or edit the security bullet "Update `bind` and `libpng` to fix outstanding CVEs"
to remove the claim about libpng (or indicate it’s handled upstream) and link to
the package list or CVE entry; update the "libpng" text in the release note and
the base distro package list consistently so the change is traceable.
---
Nitpick comments:
In `@docs/unraid-os/release-notes/7.3.0.md`:
- Line 143: Update the `dynamix.unraid.net` 4.32.3 line so its link points to
the specific 4.32.3 release tag/page instead of the generic releases page
(replace the current https://github.com/unraid/api/releases URL with the exact
release URL for 4.32.3); ensure the display text still reads "dynamix.unraid.net
4.32.3" and the link targets the precise 4.32.3 release for traceability.
- Around line 69-70: The bold "Important" sentence is split across lines which
can break some Markdown renderers; edit the release note text so the entire
sentence "**Important: Docker has been updated from v27 (in 7.2.4) to v29. This
changes how MAC addresses are allocated to containers and randomizes them.**"
appears on a single line (no hard line breaks inside the bold markers) and leave
surrounding blank lines intact to preserve paragraph separation.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 7a7fb9a3-8075-4fe3-8c78-ff2ce6a3ce7c
📒 Files selected for processing (1)
docs/unraid-os/release-notes/7.3.0.md
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
unraid-docs | dd2ae88 | Commit Preview URL Branch Preview URL |
Apr 22 2026, 08:22 PM |
- Purpose: resolve review feedback about an untraceable libpng security mention. - Before: the security section named libpng, but the base distro package list did not include a libpng version. - Why: release-note security claims should map cleanly to package entries or avoid unsupported package references. - What: remove the libpng claim and keep the security note scoped to bind, which is listed in the base distro package updates. - How: edits only docs/unraid-os/release-notes/7.3.0.md and validates with targeted markdown checks.
- Purpose: keep the 7.3.0-rc.1 Docker MAC address notes concise. - Before: the Docker section included both the new fixed-MAC field and a separate preservation fix bullet. - Why: the two bullets described overlapping behavior and made the changelog read as duplicated. - What: keep the new fixed-MAC template field entry and remove the older preservation fix line. - How: updates only docs/unraid-os/release-notes/7.3.0.md and validates with targeted markdown checks.
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/unraid-os/release-notes/7.3.0.md`:
- Around line 68-70: The bold markdown is broken because the closing "**" is on
its own line; edit the text so the opening "**" before "Important: Docker has
been updated..." and the closing "**" are on the same line (move the standalone
closing "**" into the end of the sentence so the entire sentence "**Important:
Docker has been updated from v27 (in 7.2.4) to v29. This changes how MAC
addresses are allocated to containers and randomizes them.**" is wrapped
correctly).
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: bb2c3e99-1b4e-47d7-822f-a62a93bfadb7
📒 Files selected for processing (1)
docs/unraid-os/release-notes/7.3.0.md
Comment on lines
+68
to
+70
| **Important: Docker has been updated from v27 (in 7.2.4) to v29. This changes how MAC addresses are allocated to containers and randomizes them. | ||
| ** | ||
|
|
Contributor
There was a problem hiding this comment.
Fix broken bold markdown formatting.
The closing ** is on its own line (line 69), which breaks the bold formatting. It should be moved to the end of the sentence on line 68.
📝 Proposed fix
-**Important: Docker has been updated from v27 (in 7.2.4) to v29. This changes how MAC addresses are allocated to containers and randomizes them.
-**
+**Important: Docker has been updated from v27 (in 7.2.4) to v29. This changes how MAC addresses are allocated to containers and randomizes them.**
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| **Important: Docker has been updated from v27 (in 7.2.4) to v29. This changes how MAC addresses are allocated to containers and randomizes them. | |
| ** | |
| **Important: Docker has been updated from v27 (in 7.2.4) to v29. This changes how MAC addresses are allocated to containers and randomizes them.** | |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/unraid-os/release-notes/7.3.0.md` around lines 68 - 70, The bold
markdown is broken because the closing "**" is on its own line; edit the text so
the opening "**" before "Important: Docker has been updated..." and the closing
"**" are on the same line (move the standalone closing "**" into the end of the
sentence so the entire sentence "**Important: Docker has been updated from v27
(in 7.2.4) to v29. This changes how MAC addresses are allocated to containers
and randomizes them.**" is wrapped correctly).
This was referenced Apr 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
The existing page still reflected the beta.2 release-note structure. The rc.1 notes need to describe the full 7.3.0 surface area, including onboarding/internal boot, Docker and storage changes, hardware support, virtualization updates, API/kernel updates, and package refreshes.
Validation
git diff --check -- docs/unraid-os/release-notes/7.3.0.mdpnpm exec remark docs/unraid-os/release-notes/7.3.0.md --quiet --frailPer repo guidance, I did not run the full docs build.
Summary by CodeRabbit