fix: hide reboot notice for patch releases

[elibosley]

Summary by CodeRabbit

• New Features
  • Updated the user feedback display to conditionally show the reboot reminder based on the update version type, ensuring accurate messaging for both update and downgrade scenarios.

[coderabbitai]

Walkthrough

The pull request modifies the CallbackFeedback.vue component to include conditional rendering. A v-if directive now checks if callbackUpdateRelease.version does not include the string 'patch' before displaying the paragraph element with reboot instructions. No changes were made to exported or public entities, and the component’s control flow now conditionally renders content based on the version type.

Changes

File(s)	Change Summary
web/.../CallbackFeedback.vue	Added a v-if directive to conditionally render a reboot-required message when the version does not include 'patch'.

Sequence Diagram(s)

sequenceDiagram
    participant C as CallbackFeedback.vue
    participant V as callbackUpdateRelease
    participant T as Template/DOM
    C->>V: Check if version includes "patch"
    alt Version includes "patch"
        Note over C,T: Skip rendering reboot message
    else Not a patch version
        C->>T: Render reboot message
    end

Loading

Poem

In the code's glow, a twist appears,
A patch-driven check dispelling fears,
Vue whispers logic, crisp and neat,
Rendering updates with a rhythmic beat,
CodeRabbit smiles at our revised feat!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between ff4fc76 and bf6aa31.

📒 Files selected for processing (1)

• web/components/UserProfile/CallbackFeedback.vue (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• web/components/UserProfile/CallbackFeedback.vue

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: Build Web App
• GitHub Check: Test API
• GitHub Check: Build API
• GitHub Check: Cloudflare Pages

---

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f65788a and ff4fc76.

📒 Files selected for processing (1)

• web/components/UserProfile/CallbackFeedback.vue (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: Test API
• GitHub Check: Build Web App
• GitHub Check: Build API
• GitHub Check: Cloudflare Pages

[github-actions]

This plugin has been deployed to Cloudflare R2 and is available for testing.
Download it at this URL:

https://preview.dl.unraid.net/unraid-api/tag/PR1341/dynamix.unraid.net.plg