Skip to content

fix: disable color in Homebrew service status parsing - #49

Merged
DevVig merged 1 commit into
mainfrom
fix/v0.2.1-homebrew-status-color
Jul 18, 2026
Merged

DevVig merged 1 commit into
mainfrom
fix/v0.2.1-homebrew-status-color

Conversation

@DevVig

@DevVig DevVig commented Jul 18, 2026

Copy link
Copy Markdown
Owner

Homebrew emits ANSI-colored service states on GitHub Actions. The smoke parser therefore received an escape-wrapped started value and waited until timeout even while diagnostics proved the service healthy.

This exports HOMEBREW_NO_COLOR=1 in both pre/public formula smoke and final public-install verification so service status is machine-readable. Bash syntax, workflow YAML parsing, and diff checks pass.

Copilot AI review requested due to automatic review settings July 18, 2026 19:20
@coderabbitai

coderabbitai Bot commented Jul 18, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 2 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 52245dbb-9976-4f57-aaf1-e7130ab239e4

📥 Commits

Reviewing files that changed from the base of the PR and between ee8fc80 and 29408d5.

📒 Files selected for processing (2)
  • .github/workflows/finalize-release.yml
  • scripts/smoke-formula.sh

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

@DevVig
DevVig merged commit aec4a58 into main Jul 18, 2026
8 checks passed
@DevVig
DevVig deleted the fix/v0.2.1-homebrew-status-color branch July 18, 2026 19:21

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

This PR fixes flaky Homebrew service-state parsing in CI by disabling ANSI color output from Homebrew, ensuring the smoke checks can reliably detect started/scheduled states on GitHub Actions runners.

Changes:

  • Export HOMEBREW_NO_COLOR=1 in the formula smoke script so brew services list output is machine-readable.
  • Export HOMEBREW_NO_COLOR=1 in the finalize-release workflow’s public-install verification step to prevent colorized service states from breaking the status check.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
scripts/smoke-formula.sh Disables Homebrew color output so brew services list parsing returns plain started/scheduled.
.github/workflows/finalize-release.yml Disables Homebrew color output during public-install verification to keep service-state parsing stable in CI.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants