Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@cscnk52
Copy link
Contributor

@cscnk52 cscnk52 commented Sep 18, 2025

  • 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 a Windows Scoop package manifest for installing GreptimeDB via Scoop.
    • Provides 64-bit installer with checksum verification and correct extraction path.
    • Exposes the greptime.exe command for CLI usage after install.
    • Pins initial release to version 0.17.1 with automatic update checks against GitHub releases.
    • Supports autoupdate with versioned download URLs and extraction configuration.

@coderabbitai
Copy link

coderabbitai bot commented Sep 18, 2025

Walkthrough

Adds a new Scoop manifest for GreptimeDB at bucket/greptimedb.json specifying version 0.17.1, metadata, 64-bit download URL with SHA256, extract_dir, exposed binary, checkver from GitHub, and autoupdate rules.

Changes

Cohort / File(s) Summary
Scoop manifest addition
bucket/greptimedb.json
Introduces a Scoop manifest for GreptimeDB v0.17.1 with metadata, 64-bit URL, SHA256, extract_dir, bin exposure, GitHub checkver, and versioned autoupdate configuration.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

A scoop of stars in my burrowed bowl,
GreptimeDB hops in—complete and whole.
URLs aligned, hashes tight,
Autoupdates queued for a moonlit night.
I thump, I twirl—release 0.17.1 in sight! 🐇✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Description Check ⚠️ Warning The PR description contains only the repository template with checked boxes and lacks a filled summary of the changes, any Closes/Relates issue reference, and verification/testing details (for example download URL/sha verification and install test results), so it does not satisfy the template's intent. Because these required descriptive details are missing, the description is incomplete. Update the PR description by replacing template placeholders with a concise summary of the change (new Scoop manifest for greptimedb v0.17.1), add a Closes/Relates line if an issue exists, and include brief verification notes (SHA/download checked and install tested) plus confirmation that duplicate PRs/issues were searched for.
✅ Passed checks (2 passed)
Check name Status Explanation
Title Check ✅ Passed The title "greptimedb: Add version 0.17.1" succinctly and accurately summarizes the main change — adding a new Scoop manifest for GreptimeDB pinned to v0.17.1. It follows the repository's conventional ": " format and is concise enough for a teammate scanning PR history.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 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

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

@github-actions
Copy link
Contributor

All changes look good.

Wait for review from human collaborators.

greptimedb

  • Description
  • License
  • Hashes
  • Checkver
  • Autoupdate

Check the full log for details.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (4)
bucket/greptimedb.json (4)

14-16: Use owner/repo in checkver.github (not a full URL).

Scoop’s checkver expects "github": "Owner/Repo". Using a URL may break automatic version detection.

   "checkver": {
-        "github": "https://github.com/GreptimeTeam/greptimedb"
+        "github": "GreptimeTeam/greptimedb"
   },

17-24: Add autoupdate.hash to enable automatic checksum updates.

Without a hash rule, checkver -u won’t be able to update the checksum automatically.

Option A (if a per‑asset .sha256 is published):

   "autoupdate": {
     "architecture": {
       "64bit": {
         "url": "https://github.com/GreptimeTeam/greptimedb/releases/download/v$version/greptime-windows-amd64-v$version.tar.gz",
+        "hash": {
+          "url": "$url.sha256"
+        },
         "extract_dir": "greptime-windows-amd64-v$version"
       }
     }
   }

If the project publishes a single checksums file instead, point to it and add a regex for the asset’s SHA256. I can tailor the rule once you confirm the checksums artifact name.


3-3: Tighten the description to neutral, concise wording.

Short, non‑marketing summaries are preferred in Scoop manifests.

-    "description": "Open-source, cloud-native, unified observability database for metrics, logs and traces, supporting SQL/PromQL/Streaming. Available on GreptimeCloud.",
+    "description": "Open-source, cloud-native observability database for metrics, logs, and traces; supports SQL/PromQL/streaming.",

6-12: Optional: Add arm64 architecture if an official Windows arm64 asset exists.

If Greptime publishes a Windows arm64 tarball, include it to improve coverage.

   "architecture": {
     "64bit": {
       "url": "https://github.com/GreptimeTeam/greptimedb/releases/download/v0.17.1/greptime-windows-amd64-v0.17.1.tar.gz",
       "hash": "148299e077edca9f812bb16e0b456f86be6f7338fddbf811c08c3f2d681ace1d",
       "extract_dir": "greptime-windows-amd64-v0.17.1"
-    }
+    },
+    "arm64": {
+      "url": "https://github.com/GreptimeTeam/greptimedb/releases/download/v0.17.1/greptime-windows-arm64-v0.17.1.tar.gz",
+      "hash": "<sha256-arm64>",
+      "extract_dir": "greptime-windows-arm64-v0.17.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 f7dcd9c and 0332b14.

📒 Files selected for processing (1)
  • bucket/greptimedb.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
🔇 Additional comments (2)
bucket/greptimedb.json (2)

13-13: Confirm greptime.exe path after extraction.

With extract_dir set, bin should be relative to that directory. Validate that the executable is at greptime.exe (not nested deeper).


8-11: Verified — release asset URL, extract_dir, and SHA256 match for v0.17.1.

Top-level folder in tarball: greptime-windows-amd64-v0.17.1; SHA256: 148299e077edca9f812bb16e0b456f86be6f7338fddbf811c08c3f2d681ace1d.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant