v2rayn-desktop: Add Avalonia UI version 7.14.12

[anacude]

Add Avalonia UI version.

• Use conventional PR title: <manifest-name[@version]|chore>: <general summary of the pull request>
• I have read the Contributing Guide

Summary by CodeRabbit

• New Features
  • Added v2rayN desktop client (version 7.14.12) to the app catalog.
  • Supports both 64-bit and ARM64 architectures with verified downloads.
  • Creates a desktop shortcut for quick access.
  • Enables data persistence to keep user settings across updates.
  • Configured autoupdate with versioned URLs for seamless future upgrades.

[coderabbitai]

Walkthrough

Adds a new Scoop bucket manifest at bucket/v2rayn-desktop.json defining v2rayN desktop version 7.14.12, including architectures (64bit, arm64), download URLs with hashes, extraction path, desktop shortcut, persistence, and autoupdate settings.

Changes

Cohort / File(s)	Summary
New Scoop manifest bucket/v2rayn-desktop.json	Added JSON manifest for v2rayN desktop v7.14.12 with 64bit/arm64 URLs, SHA256 hashes, extract_dir, desktop shortcut, persist, and autoupdate templates.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

I thump my paw—new manifest appears,
A tidy burrow of URLs and gears.
Hashes snug, shortcuts in place,
Persisting crumbs in a cozy space.
Autoupdate trails I’ll gladly hop—
Versioned carrots in a tidy crop.
Scoop, scoop—hippity, never stop!

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The pull request description retains the template placeholders and includes only a minimal summary, but it fails to fill in the required “Closes #XXXX” section with the actual issue number and does not explicitly mention the version in the summary, leaving key template sections incomplete.	Please update the description to explicitly state “Closes #16232” in the designated section and expand the summary to note that you are adding the v2rayn-desktop manifest for version 7.14.12, ensuring all template sections are fully completed.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.
Title Check	✅ Passed	The title succinctly describes the primary change by specifying the package name and the new Avalonia UI version being added, directly reflecting the manifest addition in the changeset without extraneous details.

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

All changes look good.

Wait for review from human collaborators.

v2rayn-desktop

• Lint
• Description
• License
• Hashes
• Checkver
• Autoupdate

Check the full log for details.

[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 84de3c4 and 5a8d748.

📒 Files selected for processing (1)

• bucket/v2rayn-desktop.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: WindowsPowerShell

[anacude]

Please merge the PR, thanks a lot. @z-Fng

[z-Fng]

@aliesbelik

Hi. Could you give me some advice on this, please?
Would it be better to place the manifests in the Versions bucket as it's a variant?

"Different variants of v2rayN are available:",
" ---------------------------------------------------------------------- ",
"|Variant                       |UI Framework   |dependencies           |",
"|------------------------------|---------------------------------------|",
"|extras/v2rayn                 |WPF            |.NET Desktop Runtime   |",
"|??????/v2rayn-selfcontained   |WPF            |                       |",
"|??????/v2rayn-desktop         |Avalonia UI    |                       |",
" ---------------------------------------------------------------------- "