Skip to content

feat: bump otel-collector to 0.150.1#27

Open
sht-bot wants to merge 1 commit into
mainfrom
bump-otel-collector-0.150.1
Open

feat: bump otel-collector to 0.150.1#27
sht-bot wants to merge 1 commit into
mainfrom
bump-otel-collector-0.150.1

Conversation

@sht-bot
Copy link
Copy Markdown
Contributor

@sht-bot sht-bot commented Apr 14, 2026

Automated formula bump for otel-collector.

  • Previous version: 0.147.0
  • New version: 0.150.1

Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 14, 2026

Walkthrough

Updated the Homebrew formula for OpenTelemetry Collector from version 0.147.0 to 0.150.1, changing the download URL, SHA-256 checksum, and version metadata accordingly.

Changes

Cohort / File(s) Summary
OpenTelemetry Collector Formula
Formula/otel-collector.rb
Version bump from 0.147.0 to 0.150.1 with updated download URL and SHA-256 checksum.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Suggested reviewers

  • yordis

Poem

🐰 A version hop, from one-four-seven to one-five-oh,
The checksums changed, the URLs flow,
Fresh bytes and hashes, all in a row,
Homebrew collectors dance and glow! 🍺

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically describes the main change: bumping otel-collector from version 0.147.0 to 0.150.1, which directly matches the changeset.
Description check ✅ Passed The description is directly related to the changeset, clearly stating the automated formula bump and explicitly documenting the version change from 0.147.0 to 0.150.1.

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

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch bump-otel-collector-0.150.1

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.

Copy link
Copy Markdown

@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: 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 `@Formula/otel-collector.rb`:
- Around line 4-6: The formula references a non-existent upstream release
v0.150.1 (see the url, sha256 and version fields) causing downloads to fail;
update the url, sha256 and version back to the latest published binary v0.149.0
(replace the otelcol-contrib_0.150.1_darwin_amd64.tar.gz URL with the v0.149.0
tarball URL, set the sha256 to the v0.149.0 checksum, and change version to
"0.149.0") so the formula points to a released asset, or alternatively leave a
TODO and wait until the v0.150.1 binary is published before bumping
url/sha256/version.
🪄 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b1923676-2c8b-41be-8e98-86d3f1cd9678

📥 Commits

Reviewing files that changed from the base of the PR and between d51e5e8 and f3b4dcd.

📒 Files selected for processing (1)
  • Formula/otel-collector.rb

Comment thread Formula/otel-collector.rb
Comment on lines +4 to +6
url "https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/v0.150.1/otelcol-contrib_0.150.1_darwin_amd64.tar.gz"
sha256 "c014d33c272b081a75d672d859c16eaae50443bc51b6704c04860881ab0c932c"
version "0.150.1"
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

URL="https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/v0.150.1/otelcol-contrib_0.150.1_darwin_amd64.tar.gz"
EXPECTED_SHA="c014d33c272b081a75d672d859c16eaae50443bc51b6704c04860881ab0c932c"

echo "Checking URL availability..."
curl -fILs "$URL" >/dev/null
echo "OK: asset is reachable"

echo "Checking SHA-256..."
ACTUAL_SHA="$(curl -fsSL "$URL" | shasum -a 256 | awk '{print $1}')"
echo "Actual:   $ACTUAL_SHA"
echo "Expected: $EXPECTED_SHA"

if [ "$ACTUAL_SHA" != "$EXPECTED_SHA" ]; then
  echo "ERROR: SHA-256 mismatch"
  exit 1
fi

echo "OK: SHA-256 matches"

Repository: TrogonStack/homebrew-tap

Length of output: 253


🏁 Script executed:

#!/bin/bash
# Verify SHA-256 using Python's hashlib
python3 << 'EOF'
import urllib.request
import hashlib

URL = "https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/v0.150.1/otelcol-contrib_0.150.1_darwin_amd64.tar.gz"
EXPECTED_SHA = "c014d33c272b081a75d672d859c16eaae50443bc51b6704c04860881ab0c932c"

print("Downloading and verifying SHA-256...")
try:
    with urllib.request.urlopen(URL, timeout=30) as response:
        sha256_hash = hashlib.sha256()
        while True:
            chunk = response.read(8192)
            if not chunk:
                break
            sha256_hash.update(chunk)
        
        actual_sha = sha256_hash.hexdigest()
        print(f"Actual:   {actual_sha}")
        print(f"Expected: {EXPECTED_SHA}")
        
        if actual_sha == EXPECTED_SHA:
            print("✓ SHA-256 matches")
        else:
            print("✗ SHA-256 mismatch")
except Exception as e:
    print(f"Error: {e}")
EOF

Repository: TrogonStack/homebrew-tap

Length of output: 239


🌐 Web query:

otelcol-contrib v0.150.1 release opentelemetry-collector-releases github darwin

💡 Result:

No evidence found for an otelcol-contrib v0.150.1 release as of 2026-04-14. The v0.150.0 release process for opentelemetry-collector-contrib was completed around 2026-04-13, as indicated by the core release issue #15100 where contrib v0.150.0 was tagged (https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.150.0). Official binaries are published in the opentelemetry-collector-releases repository, with the latest release being v0.149.0 on 2026-03-31 (https://github.com/open-telemetry/opentelemetry-collector-releases/releases). No v0.150.0 or v0.150.1 binary release appears in search results, and no Darwin-specific assets for v0.150.1 were located. Patch releases like .1 typically follow build failures or critical fixes, similar to past patterns (e.g., v0.130.1, v0.140.1), but none is confirmed here. Check https://github.com/open-telemetry/opentelemetry-collector-releases/releases for updates.

Citations:


The v0.150.1 release does not exist in the upstream repository.

The referenced asset at v0.150.1/otelcol-contrib_0.150.1_darwin_amd64.tar.gz cannot be downloaded because no v0.150.1 binary release has been published to the opentelemetry-collector-releases repository. The latest available binary release is v0.149.0 (March 31, 2026).

Revert to v0.149.0 or wait until the upstream v0.150.1 binary release is published.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@Formula/otel-collector.rb` around lines 4 - 6, The formula references a
non-existent upstream release v0.150.1 (see the url, sha256 and version fields)
causing downloads to fail; update the url, sha256 and version back to the latest
published binary v0.149.0 (replace the
otelcol-contrib_0.150.1_darwin_amd64.tar.gz URL with the v0.149.0 tarball URL,
set the sha256 to the v0.149.0 checksum, and change version to "0.149.0") so the
formula points to a released asset, or alternatively leave a TODO and wait until
the v0.150.1 binary is published before bumping url/sha256/version.

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.

2 participants