Skip to content

Add 7.1.3 release notes #284

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jun 4, 2025
Merged

Add 7.1.3 release notes #284

merged 3 commits into from
Jun 4, 2025

Conversation

ljm42
Copy link
Member

@ljm42 ljm42 commented Jun 3, 2025

Before Submitting This PR, Please Ensure You Have Completed The Following:

  1. Are internal links to wiki documents using relative file links?
  2. Are all new documentation files lowercase, with dash separated names (ex. unraid-os.mdx)?
  3. Are all assets (images, etc), located in an assets/ subfolder next to the .md/mdx files?
  4. Have you checked to ensure there aren't other open Pull Requests for the same update/change?
  5. Is the build succeeding?

Summary by CodeRabbit

  • Documentation
    • Updated release notes for versions 7.1.1 and 7.1.2, including new sections for VM Manager and Storage, and clarified kernel version status.
    • Added release notes for version 7.1.3, detailing bug fixes and improvements in Networking, Docker, Storage, webGUI, and base system components, along with security updates to curl.

Copy link
Contributor

coderabbitai bot commented Jun 3, 2025

📝 Walkthrough

Walkthrough

Release notes for Unraid OS versions 7.1.1, 7.1.2, and 7.1.3 have been updated and added. These updates document bug fixes across VM management, storage, networking, Docker, webGUI, kernel, and curl, with explicit notes on unchanged kernel versions. No changes to exported or public entities were made.

Changes

File(s) Change Summary
docs/unraid-os/release-notes/7.1.1.md Updated release notes: added VM Manager section for OVMF firmware fix; clarified Linux kernel version as unchanged.
docs/unraid-os/release-notes/7.1.2.md Updated release notes: now relative to 7.1.1; added Storage section for mover empty disk fix; noted unchanged kernel.
docs/unraid-os/release-notes/7.1.3.md Added new release notes for 7.1.3: details bugfixes in networking, Docker, storage, webGUI, kernel, and curl updates.

Sequence Diagram(s)

Loading
sequenceDiagram
    participant User
    participant ReleaseNotes
    User->>ReleaseNotes: Read 7.1.1 notes
    ReleaseNotes-->>User: VM Manager OVMF fix, kernel unchanged

    User->>ReleaseNotes: Read 7.1.2 notes
    ReleaseNotes-->>User: Storage (mover empty disk) fix, kernel unchanged

    User->>ReleaseNotes: Read 7.1.3 notes
    ReleaseNotes-->>User: Networking, Docker, Storage, webGUI, kernel, and curl fixes

Possibly related PRs

  • Add 7.1.1 release notes #267: Added the original 7.1.1 release notes, which are now updated in this PR with additional VM Manager and kernel information.
  • Add 7.1.2 release notes #270: Added the 7.1.2 release notes, closely related as this PR updates the same notes with further clarifications and new sections.

Poem

Three new notes for Unraid’s tale,
Bugs squashed and fixes prevail.
VMs now start, the mover’s on track,
Docker and networks no longer crack.
With kernels and curl up to date,
🐇 Cheers for a system running great!
—A rabbit with release notes on its plate


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c207c4c and 945266d.

📒 Files selected for processing (3)
  • docs/unraid-os/release-notes/7.1.1.md (1 hunks)
  • docs/unraid-os/release-notes/7.1.2.md (1 hunks)
  • docs/unraid-os/release-notes/7.1.3.md (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (3)
  • docs/unraid-os/release-notes/7.1.1.md
  • docs/unraid-os/release-notes/7.1.2.md
  • docs/unraid-os/release-notes/7.1.3.md
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: build

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-284.d1o5s833kbd339.amplifyapp.com

@ljm42 ljm42 force-pushed the add-7-1-1-rc-1-1 branch from 657203d to 945266d Compare June 4, 2025 16:38
@ljm42 ljm42 merged commit e194dc8 into main Jun 4, 2025
3 checks passed
@ljm42 ljm42 deleted the add-7-1-1-rc-1-1 branch June 4, 2025 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants