Add rose-pine/rose-pine-bloom

[yudai-nkt]

Check List

• Read CONTRIBUTING.md
  • ⚠️ Avoid force push
  • ⚠️ Use argd s command when adding new packages
• Install and execute the package and confirm if the package works well

I added a package rose-pine/rose-pine-bloom, a CLI for templating Rosé Pine palette theme for various applications.

Summary by CodeRabbit

• New Features
  • Added Rosé Pine Bloom package with native support for multiple operating systems and processor architectures, enabling platform-specific installations.

[coderabbitai]

Warning

Rate limit exceeded

@suzuki-shunsuke has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 53 minutes and 15 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 53 minutes and 15 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b4bc3435-b70a-4ec8-bb95-60e076ce747d

📥 Commits

Reviewing files that changed from the base of the PR and between 2eb3e19 and 301b988.

📒 Files selected for processing (2)

• pkgs/rose-pine/rose-pine-bloom/registry.yaml
• registry.yaml

📝 Walkthrough

Walkthrough

Three YAML configuration files are added to register the rose-pine/rose-pine-bloom package, including a package manifest, package-specific registry configuration with version constraints and asset overrides, and a main registry entry defining GitHub release-based package retrieval logic.

Changes

Cohort / File(s)	Summary
Rose Pine Bloom Package Registration pkgs/rose-pine/rose-pine-bloom/pkg.yaml, pkgs/rose-pine/rose-pine-bloom/registry.yaml, registry.yaml	Added package manifest entry and registry configurations for rose-pine/rose-pine-bloom@v3.0.1. Configuration defines github_release source with version-specific overrides: v3.0.0 disables asset retrieval, other versions fetch OS/arch-specific assets named rose-pine-bloom-{{.OS}}-{{.Arch}}.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested labels

enhancement

Poem

🌹 A bloom of roses in the registry we place,
Pink petals guide the package to its place,
With versions wise, we override with care,
Let developers paint themes everywhere! 🐰✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: scaffolding a new package entry for rose-pine/rose-pine-bloom, which aligns with the changeset additions.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description check	✅ Passed	The PR description includes all required checklist items marked as completed and provides a clear explanation of the package being added.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@pkgs/rose-pine/rose-pine-bloom/pkg.yaml`:
- Around line 1-2: Add a second package entry for the older release to exercise
the no_asset override: alongside the existing short-form entry with name
"rose-pine/rose-pine-bloom@v3.0.1", add a long-form package entry for v3.0.0
that separates the package name and version (e.g. an object with keys like name:
"rose-pine/rose-pine-bloom" and version: "v3.0.0") so the registry uses the
no_asset path and the version is pinned (prevents automatic updates).

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: f6ec1cff-c6c6-4650-a5d3-c31300f8ef6d

📥 Commits

Reviewing files that changed from the base of the PR and between 9ba5fd0 and 2eb3e19.

📒 Files selected for processing (3)

• pkgs/rose-pine/rose-pine-bloom/pkg.yaml
• pkgs/rose-pine/rose-pine-bloom/registry.yaml
• registry.yaml

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check GitHub releases for rose-pine/rose-pine-bloom to verify asset availability

echo "=== Checking v3.0.0 assets ==="
gh api repos/rose-pine/rose-pine-bloom/releases/tags/v3.0.0 --jq '.assets[] | .name' || echo "No assets or release not found"

echo ""
echo "=== Checking v3.0.1 assets ==="
gh api repos/rose-pine/rose-pine-bloom/releases/tags/v3.0.1 --jq '.assets[] | .name' || echo "No assets or release not found"

echo ""
echo "=== Latest releases ==="
gh api repos/rose-pine/rose-pine-bloom/releases --jq '.[:3] | .[] | {tag: .tag_name, asset_count: (.assets | length), assets: [.assets[].name]}'

Repository: aquaproj/aqua-registry

Length of output: 662

---

🏁 Script executed:

# First, find and examine the registry.yaml entries for rose-pine/rose-pine-bloom
rg -A 30 "rose-pine/rose-pine-bloom" registry.yaml

Repository: aquaproj/aqua-registry

Length of output: 48

---

🏁 Script executed:

# Try broader search for rose-pine-bloom
rg "rose-pine-bloom" registry.yaml

# Also check the directory to understand structure
ls -la pkgs/rose-pine/rose-pine-bloom/

# Check if registry.yaml file exists and has content
wc -l registry.yaml

Repository: aquaproj/aqua-registry

Length of output: 393

---

🏁 Script executed:

# Read the local registry.yaml and pkg.yaml for rose-pine-bloom
echo "=== pkg.yaml ===" 
cat -n pkgs/rose-pine/rose-pine-bloom/pkg.yaml

echo ""
echo "=== registry.yaml ==="
cat -n pkgs/rose-pine/rose-pine-bloom/registry.yaml

Repository: aquaproj/aqua-registry

Length of output: 739

---

🌐 Web query:

rose-pine/rose-pine-bloom v3.0.0 GitHub release assets

💡 Result:

GitHub release rose-pine/rose-pine-bloom v3.0.0 has 2 release assets (the default GitHub-generated source archives): (github.com)

• Source code (zip): https://github.com/rose-pine/rose-pine-bloom/archive/refs/tags/v3.0.0.zip
• Source code (tar.gz): https://github.com/rose-pine/rose-pine-bloom/archive/refs/tags/v3.0.0.tar.gz

Citations:

• 1: https://github.com/rose-pine/rose-pine-bloom/releases/tag/v3.0.0

---

🌐 Web query:

rose-pine/rose-pine-bloom v3.0.1 GitHub release binary assets

💡 Result:

The GitHub release rose-pine/rose-pine-bloom v3.0.1 (dated 2025-11-17) shows “Assets 8” on the release page, but GitHub renders the asset filenames client-side and they aren’t available in the HTML snapshot I can fetch here (it only shows “Assets 8” + “Loading”). [1]

To list the exact binary asset names/URLs, use one of these:

• GitHub CLI

  gh release view v3.0.1 -R rose-pine/rose-pine-bloom --json assets \
    -q '.assets[] | [.name, .size, .browser_download_url] | `@tsv`'

• GitHub API (curl + jq)

  curl -sL https://api.github.com/repos/rose-pine/rose-pine-bloom/releases/tags/v3.0.1 \
    | jq -r '.assets[] | [.name, .size, .browser_download_url] | `@tsv`'

Source:
[1] Release page showing v3.0.1 and “Assets 8” — https://github.com/rose-pine/rose-pine-bloom/releases/tag/v3.0.1

---

Add v3.0.0 to test the no_asset override path.

The registry.yaml defines two distinct version_overrides:

• v3.0.0: no_asset: true (no custom binary assets available)
• Other versions: asset template with format: raw (custom binaries available)

These different configurations exercise different code paths. Currently, only v3.0.1 is tested (the asset path), but v3.0.0 (the no_asset path) should also be tested. Use long syntax for older versions to prevent automatic updates.

Suggested addition

 packages:
+  - name: rose-pine/rose-pine-bloom
+    version: v3.0.0
   - name: rose-pine/rose-pine-bloom@v3.0.1

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	packages:
	- name: rose-pine/rose-pine-bloom@v3.0.1
	packages:
	- name: rose-pine/rose-pine-bloom
	version: v3.0.0
	- name: rose-pine/rose-pine-bloom@v3.0.1

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@pkgs/rose-pine/rose-pine-bloom/pkg.yaml` around lines 1 - 2, Add a second
package entry for the older release to exercise the no_asset override: alongside
the existing short-form entry with name "rose-pine/rose-pine-bloom@v3.0.1", add
a long-form package entry for v3.0.0 that separates the package name and version
(e.g. an object with keys like name: "rose-pine/rose-pine-bloom" and version:
"v3.0.0") so the registry uses the no_asset path and the version is pinned
(prevents automatic updates).

[suzuki-shunsuke]

Thank you!

[suzuki-shunsuke]

🎉 https://github.com/aquaproj/aqua-registry/releases/tag/v4.494.0