Uh oh!
There was an error while loading. Please reload this page.
docs: update Unraid OS 7.2.5-rc.2 changelog - #462
Merged
Conversation
- Purpose: update the Unraid OS 7.2.5 release notes for the final non-RC build. - Before: the page still identified the release as 7.2.5-rc.1 and showed the older unchanged kernel line. - Problem: final release notes would omit the final kernel security update and the runc CVE context in the Docker update. - Change: mark the release as 7.2.5 dated 2026-04-20, add the runc CVE summary, update the Unraid API wording, and document Linux 6.12.82-Unraid with CVE-2026-31430. - How: edit the single 7.2.5 release-note Markdown file and validate with targeted Markdown lint plus whitespace checks.
Contributor
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughUpdated release notes from Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Deploying with |
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs | unraid-docs | 216061c | Commit Preview URL Branch Preview URL | Apr 20 2026, 07:31 PM |
- Purpose: update the Unraid OS 7.2.5 changelog to the final API package version. - Before: the release note listed dynamix.unraid.net 4.32.2. - Problem: the PR would publish an outdated API version for the final 7.2.5 release. - Change: replace the Unraid API entry with dynamix.unraid.net 4.32.3. - How: edit the single release-note line and validate with targeted Markdown lint plus whitespace checks.
- Purpose: change the 7.2.5 release note from final-release wording to 7.2.5-rc.2. - Before: the page title identified the release as 7.2.5 and the changelog compared against 7.2.4. - Problem: the PR needed to represent rc.2 and call out changes from rc.1 while preserving the existing release-note wording. - Change: retitle the page to 7.2.5-rc.2, change the heading to changes from rc.1, keep the existing Docker, Tailscale, storage, WebGUI, API, kernel, and base distro wording, and add the rare-crash mitigation. - How: edit the single 7.2.5 release-note Markdown file and validate with targeted Markdown lint plus whitespace checks.
- Purpose: make the 7.2.5-rc.2 changelog clear about what changed after rc.1. - Before: the heading said changes from rc.1, but carried-forward rc.1 entries were listed under the same section. - Problem: readers could interpret Docker, storage, WebGUI, API, and base distro entries as new rc.2 changes. - Change: state that only the kernel update and rare-crash mitigation are new in rc.2, then move the older entries under an Included from rc.1 section. - How: restructure the Markdown sections without changing the carried-forward entry text.
- Purpose: clarify that the dynamix.unraid.net 4.32.3 update is new in 7.2.5-rc.2. - Before: the API version line was listed under Included from rc.1 even though it changed from 4.32.2 to 4.32.3. - Problem: the changelog understated the rc.2 delta and could make the API bump look carried over from rc.1. - Change: move the 4.32.3 API version line into Changes from rc.1 and update the rc.2 delta sentence. - How: preserve the rc.1 registration-state fix under Included from rc.1 while listing only the API version bump in the rc.2 section.
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 freeto 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
Full build intentionally not run, per repo guidance for routine docs validation.
Summary by CodeRabbit
Documentation
Security
Bug Fixes
Updates