vivid: Add version 0.10.1

[noidilin]

Added a manifest for vivid version 0.10.1.

Close ScoopInstaller/Main#7223

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

Summary

• support 32bit and 64bit
• choose msvc as default in convention and for broader compatibility

Summary by CodeRabbit

• New Features

  • Added the vivid tool to the package collection for easy Windows installation.
  • Supports both 64-bit and 32-bit MSVC builds with verified downloads.
  • Automatic release tracking and autoupdate support for seamless updates.
  • Installs vivid.exe for immediate command-line use.

• Documentation

  • Includes usage notes and suggested prerequisites to guide setup.

[coderabbitai]

Walkthrough

Adds a new Scoop manifest bucket/vivid.json for the vivid tool (v0.10.1) including metadata, notes, suggests, architecture-specific download entries and hashes, bin mapping, checkver: github, and autoupdate templates for 64-bit and 32-bit Windows MSVC builds.

Changes

Cohort / File(s)	Summary
New Scoop manifest: vivid bucket/vivid.json	Adds manifest for vivid v0.10.1 with description, homepage, license, notes, suggests, architecture-specific download blocks (x86_64 and i686 Windows MSVC) including url, hash, and extract_dir, bin mapping to vivid.exe, checkver: github, and autoupdate templates using $version.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Assessment against linked issues

Objective	Addressed	Explanation
Popularity/repute and English interface/docs (#16099)	✅
Latest stable version v0.10.1 (#16099)	✅
Full version (non-trial) (#16099)	✅
Fairly standard install: versioned URL, no elaborate scripts (#16099)	✅

I hopped through buckets, light and spry,
Found vivid hues for LS_COLORS' sky.
A zip to fetch, a bin to bind—
Autoupdate set, release aligned.
Hashes checked, the rabbit's signed. 🐇🌈

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 972d979 and 7b0cedc.

📒 Files selected for processing (1)

• bucket/vivid.json (1 hunks)

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

• bucket/vivid.json

✨ Finishing Touches

🧪 Generate unit tests

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

---

🪧 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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit 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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.

[github-actions]

All changes look good.

Wait for review from human collaborators.

vivid

• Description
• License
• Hashes
• Checkver
• Autoupdate

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (2)

bucket/vivid.json (2)

6-15: Tune notes for Windows and trim deprecated tooling.

• Include a PowerShell example alongside the POSIX export to reduce confusion.
• Consider dropping exa (deprecated upstream) and highlight eza/lsd which honor LS_COLORS on Windows.

     "notes": [
-        "vivid generates LS_COLORS for colorizing file listings in terminals.",
-        "Requires GNU coreutils (ls) or compatible tools to display colors:",
-        "  scoop install coreutils",
-        "  scoop install extras/exa",
-        "  scoop install extras/lsd",
-        "",
-        "Usage: export LS_COLORS=\"$(vivid generate molokai)\"",
-        "Available themes: vivid themes"
+        "vivid generates LS_COLORS for colorizing file listings.",
+        "Tools that use LS_COLORS on Windows include eza and lsd; GNU coreutils ls also works:",
+        "  scoop install coreutils",
+        "  scoop install eza",
+        "  scoop install extras/lsd",
+        "",
+        "POSIX shells:   export LS_COLORS=\"$(vivid generate molokai)\"",
+        "PowerShell:     $env:LS_COLORS = (vivid.exe generate molokai)",
+        "Available themes: vivid themes"
     ],

---

16-19: Adjust suggest bucket qualifiers.

eza lives in main; exa is deprecated. Suggest listing eza and lsd; keep coreutils.

     "suggest": {
         "GNU coreutils": "coreutils",
-        "Modern ls alternatives": ["extras/exa", "extras/lsd", "extras/eza"]
+        "Modern ls alternatives": ["eza", "extras/lsd"]
     },

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between f2a599c and 972d979.

📒 Files selected for processing (1)

• bucket/vivid.json (1 hunks)

🔇 Additional comments (3)

bucket/vivid.json (3)

1-47: Solid, complete manifest overall.

URLs, extract_dir, bin, checkver, and autoupdate patterns look consistent with the upstream v0.10.1 release. Nice job supporting both 64-bit and 32-bit MSVC builds. (github.com)

---

33-45: Autoupdate and checkver look correct.

Patterns match upstream naming; extract_dir templates are aligned with asset folders. No changes needed.

(github.com)

---

21-30: Manual verification required
Automated SHA256 checks failed due to SSL certificate errors. Please manually download both Windows MSVC zip assets for v0.10.1 and confirm their SHA256 hashes match those in bucket/vivid.json before merging.

[aliesbelik]

ScoopInstaller/Main#6718

[z-Fng]

@noidilin Thanks! I've added you as a co-author of ScoopInstaller/Main#6718.

[z-Fng]

Closing this as ScoopInstaller/Main#6718 has been merged.