CI: use macos-latest for release build#79
Conversation
|
Warning Rate limit exceeded
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 19 minutes and 12 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the 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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughUpdated the macOS build job runner in CI from a pinned image to the floating latest image; made gettext PATH setup conditional in the macOS build script to use Homebrew when present; appended Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
🧹 Nitpick comments (1)
contrib/dash/actions/script-osx.sh (1)
31-36: Address shellcheck warning: declare and assign separately to avoid masking return values.The
export PATH="$(brew --prefix gettext)/bin:$PATH"pattern masks the exit code ofbrew --prefix gettext. If gettext isn't installed via Homebrew, this fails silently and adds an invalid path.♻️ Proposed fix to separate declaration and assignment
if command -v brew >/dev/null 2>&1; then - export PATH="$(brew --prefix gettext)/bin:$PATH" + GETTEXT_PREFIX="$(brew --prefix gettext)" + export PATH="${GETTEXT_PREFIX}/bin:$PATH" else export PATH="/usr/local/opt/gettext/bin:$PATH" fi🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@contrib/dash/actions/script-osx.sh` around lines 31 - 36, The export currently masks brew's exit code; change to first capture brew's prefix into a variable (e.g., gettext_prefix=$(brew --prefix gettext 2>/dev/null)), check its success/that the directory exists, and only then export PATH="$gettext_prefix/bin:$PATH"; if that check fails fall back to exporting PATH="/usr/local/opt/gettext/bin:$PATH". Keep the existing command -v brew check and use the captured gettext_prefix when updating PATH so brew's failure isn't silently masked.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@contrib/dash/actions/script-osx.sh`:
- Around line 31-36: The export currently masks brew's exit code; change to
first capture brew's prefix into a variable (e.g., gettext_prefix=$(brew
--prefix gettext 2>/dev/null)), check its success/that the directory exists, and
only then export PATH="$gettext_prefix/bin:$PATH"; if that check fails fall back
to exporting PATH="/usr/local/opt/gettext/bin:$PATH". Keep the existing command
-v brew check and use the captured gettext_prefix when updating PATH so brew's
failure isn't silently masked.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: ddc3a711-5e9e-4f60-bd7f-1bdafcf427ae
📒 Files selected for processing (2)
.github/workflows/build_release.ymlcontrib/dash/actions/script-osx.sh
No description provided.