Merged
Conversation
- Purpose: prepare the 7.2.5 release notes from the latest Asana draft on a branch based on current main. - Before: main still carried the 7.2.5-rc.2 notes with an rc-by-rc structure and older package/kernel details. - Problem: those notes did not reflect the final-style release summary, package CVE coverage, Docker MAC address guidance, or updated API/kernel details. - Now: the 7.2.5 page is rewritten as final release notes with consolidated sections, updated package/version details, and the mover empty-disk documentation link. - How: replace the rc.2 delta structure with the current final changelog content while preserving the existing upgrade, known-issues, and rollback scaffolding.
Contributor
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
Disabled knowledge base sources:
📝 WalkthroughWalkthroughUnraid 7.2.5 release notes are updated with an expanded "BREAKING CHANGES" section documenting Docker MAC address generation behavior, security fixes for WebGUI and kernel CVEs, extended Docker runc fixes, storage partition-layout improvements, Unraid API updates, and a comprehensive base distro updates and CVEs list. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
Review rate limit: 4/5 reviews remaining, refill in 12 minutes. Comment |
- Purpose: call out the Linux kernel upgrade for the newly disclosed Copy Fail vulnerability. - Before: the 7.2.5 notes mentioned the kernel version and CVE-2026-31430 but did not name CVE-2026-31431 or Copy Fail. - Problem: readers would miss that the release also includes kernel coverage for the new local privilege escalation issue. - Now: the opening release body, security section, and Linux kernel section all mention CVE-2026-31431, the Copy Fail local privilege escalation vulnerability. - How: add the Copy Fail language to the existing final release-note draft without changing unrelated sections.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
unraid-docs | fda9cf9 | Commit Preview URL Branch Preview URL |
Apr 30 2026, 09:10 PM |
elibosley
changed the title
- Purpose: make the 7.2.5 notes explicitly reference the runc security fixes included with the Docker update. - Before: the final release-note draft mentioned Docker 29 but did not call out the runc CVEs from the earlier release-note body. - Problem: readers could miss that the Docker update includes runc fixes for CVE-2025-31133, CVE-2025-52565, and CVE-2025-52881. - Now: the opening release body and Containers / Docker section both include the runc CVE references. - How: add one summary sentence near the top and one Docker security bullet without changing unrelated sections.
- Purpose: align the 7.2.5 package update list with the preferred release-note format. - Before: package entries included architecture suffixes and an extra ngtcp2 added-package line. - Problem: the section was noisier than the source package summary and did not preserve the preferred upgrade arrow marker. - Now: the package list uses simplified version strings, keeps the upgrade arrow glyph, and removes the ngtcp2 entry. - How: update only the Base distro updates and CVEs section.
- Purpose: include the ngtcp2 package addition in the 7.2.5 base distro update list. - Before: the simplified package update pass removed ngtcp2 from the public release notes. - Problem: the package section was missing an added package that should remain visible in the release summary. - Now: the package list includes an arrow-marked ngtcp2 entry with the simplified added version. - How: add to the Base distro updates and CVEs section.
- Purpose: match the preferred package update notation in the 7.2.5 notes. - Before: package update entries used ASCII arrows between old and new versions. - Problem: the section did not match the requested visual format for package changes. - Now: package update entries use the right-arrow glyph between versions while keeping the existing upgrade glyph on each line. - How: replace version separator arrows in the Base distro updates and CVEs section.
- Purpose: distinguish added packages from upgraded packages in the 7.2.5 package update list. - Before: ngtcp2 used the same upgrade arrow marker as packages with old and new versions. - Problem: that implied ngtcp2 was upgraded rather than newly added. - Now: ngtcp2 uses a plus marker while upgraded packages keep the up-arrow marker. - How: change only the ngtcp2 package list marker in the release notes.
- Purpose: restore the Unraid API release link and clean up redundant security wording. - Before: the Unraid API line no longer linked to the API releases page, and the Security section repeated the word Security in the kernel bullet. - Problem: readers lost a useful source link and the kernel security entry read awkwardly under its own Security heading. - Now: the API update links to the upstream releases page, and the kernel bullet starts directly with the upgrade action. - How: update only the Unraid API bullet and the Security section kernel bullet.
- Purpose: align the 7.2.5 changelog heading and CVE coverage note with the release date. - Before: the 7.2.5 heading lacked a date, and the package CVE coverage note said Apr 29, 2026. - Problem: neighboring changelogs include dates in the heading, and the CVE coverage note needed the Apr 30 date. - Now: the heading reads Version 7.2.5 2026-04-30, and the package CVE coverage note says Apr 30, 2026. - How: update the release-note heading and the Security section CVE coverage sentence.
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
Validation
git diff --checkpnpm exec remark docs/unraid-os/release-notes/7.2.5.md --quiet --frailpnpm exec prettier --check docs/unraid-os/release-notes/7.2.5.mdFull build intentionally not run for this docs-only change.
Summary by CodeRabbit
New Features
Breaking Changes
Bug Fixes