Skip to content

blocmcp: bump to v0.1.8 - #13

Merged
tiljrd merged 1 commit into
mainfrom
bump/v0.1.8
Nov 21, 2025
Merged

blocmcp: bump to v0.1.8#13
tiljrd merged 1 commit into
mainfrom
bump/v0.1.8

Conversation

@tiljrd

@tiljrd tiljrd commented Nov 21, 2025

Copy link
Copy Markdown
Contributor

User description

Automated update


PR Type

Enhancement


Description

  • Update blocmcp formula version from 0.1.7 to 0.1.8

  • Update download URLs for all platform variants

  • Update SHA256 checksums for macOS and Linux builds


Diagram Walkthrough

flowchart LR
  A["blocmcp v0.1.7"] -- "version bump" --> B["blocmcp v0.1.8"]
  B -- "update URLs" --> C["macOS arm64/amd64"]
  B -- "update URLs" --> D["Linux arm64/amd64"]
  C -- "new checksums" --> E["Release artifacts"]
  D -- "new checksums" --> E
Loading

File Walkthrough

Relevant files
Configuration changes
blocmcp.rb
Version bump and checksum updates for v0.1.8                         

Formula/blocmcp.rb

  • Bumped version from 0.1.7 to 0.1.8
  • Updated download URLs for all four platform variants (macOS
    arm64/amd64, Linux arm64/amd64)
  • Updated SHA256 checksums for all platform builds to match new release
    artifacts
+9/-9     

Summary by CodeRabbit

  • Chores
    • Released version 0.1.8 with updated binaries for all supported platforms (macOS and Linux).

✏️ Tip: You can customize this high-level summary in your review settings.

@qodo-code-review

Copy link
Copy Markdown

You are nearing your monthly Qodo Merge usage quota. For more information, please visit here.

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢
No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
🎫 No ticket provided
  • Create ticket/issue
Codebase Duplication Compliance
Codebase context is not defined

Follow the guide to enable codebase context checks.

Custom Compliance
🟢
Generic: Comprehensive Audit Trails

Objective: To create a detailed and reliable record of critical system actions for security analysis
and compliance.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Meaningful Naming and Self-Documenting Code

Objective: Ensure all identifiers clearly express their purpose and intent, making code
self-documenting

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Robust Error Handling and Edge Case Management

Objective: Ensure comprehensive error handling that provides meaningful context and graceful
degradation

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Secure Error Handling

Objective: To prevent the leakage of sensitive system information through error messages while
providing sufficient detail for internal debugging.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Secure Logging Practices

Objective: To ensure logs are useful for debugging and auditing without exposing sensitive
information like PII, PHI, or cardholder data.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Security-First Input Validation and Data Handling

Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent
vulnerabilities

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend 🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

@coderabbitai

coderabbitai Bot commented Nov 21, 2025

Copy link
Copy Markdown

Walkthrough

The blocmcp formula version is bumped from 0.1.7 to 0.1.8, with all platform-specific download URLs and SHA-256 checksums updated accordingly for macOS ARM64, macOS AMD64, Linux ARM64, and Linux AMD64.

Changes

Cohort / File(s) Summary
Version and artifact update
Formula/blocmcp.rb
Bumps version from 0.1.7 to 0.1.8 and updates all platform-specific download URLs and corresponding SHA-256 checksums

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

This is a straightforward, mechanical version bump with repetitive updates to URLs and checksums across multiple platforms. The changes are low-risk and follow a consistent pattern.

Possibly related PRs

Suggested labels

Review effort 2/5

Poem

🐰 A version hops from eight to eight's new friend,
Checksums verified from start to end,
Four platforms blessed with URLs so fresh,
No logic changed, just artifacts refreshed! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The pull request title 'blocmcp: bump to v0.1.8' directly summarizes the main change—updating the blocmcp formula version from 0.1.7 to 0.1.8.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch bump/v0.1.8

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 75f262a and 4137f30.

📒 Files selected for processing (1)
  • Formula/blocmcp.rb (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). (3)
  • GitHub Check: test-bot (macos-26)
  • GitHub Check: test-bot (macos-15-intel)
  • GitHub Check: test-bot (ubuntu-22.04)
🔇 Additional comments (2)
Formula/blocmcp.rb (2)

4-4: LGTM: Version bump is consistent.

The version update to "0.1.8" aligns with the PR objectives and is consistently applied throughout the formula.


10-24: Release artifacts and checksums verified successfully.

All four platform-specific URLs and SHA-256 checksums for version 0.1.8 have been confirmed. The GitHub release v0.1.8 exists and is published, with all artifacts and corresponding official .sha256 files present. All checksums in the formula match the official release checksums exactly.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

  • Provide your own instructions using the high_level_summary_instructions setting.
  • Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
  • Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

  1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
  2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
  3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
  4. 📊 Contributor Summary — Include a Markdown table showing contributions:
    | Contributor | Lines Added | Lines Removed | Files Changed |
  5. ✔️ Additional Notes — Add any extra reviewer context.
    Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.


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.

@qodo-code-review

Copy link
Copy Markdown

You are nearing your monthly Qodo Merge usage quota. For more information, please visit here.

PR Code Suggestions ✨

Explore these optional code suggestions:

CategorySuggestion                                                                                                                                    Impact
General
Use version variable in URLs

Refactor the hardcoded version 0.1.8 in the download URLs to use the version
variable via string interpolation to simplify future updates.

Formula/blocmcp.rb [8-26]

 on_macos do
   if Hardware::CPU.arm?
-    url "https://github.com/0xBloctopus/homebrew-tap/releases/download/v0.1.8/blocmcp_v0.1.8_darwin_arm64.tar.gz"
+    url "https://github.com/0xBloctopus/homebrew-tap/releases/download/v#{version}/blocmcp_v#{version}_darwin_arm64.tar.gz"
     sha256 "989e9ef77df8b6309757b95ee3396eb1d4af091407630c2646d81aed5b439471"
   else
-    url "https://github.com/0xBloctopus/homebrew-tap/releases/download/v0.1.8/blocmcp_v0.1.8_darwin_amd64.tar.gz"
+    url "https://github.com/0xBloctopus/homebrew-tap/releases/download/v#{version}/blocmcp_v#{version}_darwin_amd64.tar.gz"
     sha256 "74cda1bed42de2903fabfba5425ba3af54a39d7e79865af81cd56d6870463482"
   end
 end
 
 on_linux do
   if Hardware::CPU.arm?
-    url "https://github.com/0xBloctopus/homebrew-tap/releases/download/v0.1.8/blocmcp_v0.1.8_linux_arm64.tar.gz"
+    url "https://github.com/0xBloctopus/homebrew-tap/releases/download/v#{version}/blocmcp_v#{version}_linux_arm64.tar.gz"
     sha256 "19ac6d1378a1d8f7ba40d01e2b7f552c929b8201a01926021f779b048e6a2c93"
   else
-    url "https://github.com/0xBloctopus/homebrew-tap/releases/download/v0.1.8/blocmcp_v0.1.8_linux_amd64.tar.gz"
+    url "https://github.com/0xBloctopus/homebrew-tap/releases/download/v#{version}/blocmcp_v#{version}_linux_amd64.tar.gz"
     sha256 "c2dad1cfeb969e26783a70988b494e761ffad5f59186fa85507108c9b6dcc600"
   end
 end
  • Apply / Chat
Suggestion importance[1-10]: 7

__

Why: The suggestion correctly proposes using the version variable in the URL strings to improve maintainability, which is a standard best practice for Homebrew formulas.

Medium
  • More

@tiljrd
tiljrd merged commit e9aa9cd into main Nov 21, 2025
5 checks passed
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