Skip to content

fix: soft_fail covers the channel-compat install step - #74

Merged
JarbasAl merged 1 commit into
devfrom
fix/channel-compat-self-exclusion
Aug 1, 2026
Merged

fix: soft_fail covers the channel-compat install step#74
JarbasAl merged 1 commit into
devfrom
fix/channel-compat-self-exclusion

Conversation

@JarbasAl

@JarbasAl JarbasAl commented Aug 1, 2026

Copy link
Copy Markdown
Member

Follow-up to #72: the first caller runs surfaced a real fleet finding — dev ovos-core's ovos-messagebus>=0.2.1a1 floor is unsatisfiable under constraints-stable (<0.1.0) — but it failed the job at the install step, which the test-step continue-on-error cannot reach. In advisory (soft_fail) mode the unresolvable channel now lands in the step summary as a warning, the test step is skipped, and the job stays green; with soft_fail: false the install failure still fails the job.

Found by the ovos-core/ovos-workshop reference callers; fix by Claude Fable directly.

🤖 Generated with Claude Code

An unsatisfiable channel resolve (repo floors outgrew the channel,
e.g. dev ovos-core needs ovos-messagebus>=0.2.1a1 vs stable's <0.1.0)
failed the job at install, out of reach of the test step's
continue-on-error. Advisory mode now reports it as a summary warning
and skips the test step instead.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Aug 1, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@JarbasAl, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 47 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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 18a97239-346e-4333-a2e4-ac62668eb867

📥 Commits

Reviewing files that changed from the base of the PR and between 2f7c7b5 and 86ce604.

📒 Files selected for processing (1)
  • .github/workflows/channel-compat.yml

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.

@JarbasAl
JarbasAl marked this pull request as ready for review August 1, 2026 16:27
@JarbasAl
JarbasAl merged commit 5fe1bb7 into dev Aug 1, 2026
1 check passed
@JarbasAl
JarbasAl deleted the fix/channel-compat-self-exclusion branch August 1, 2026 16:27
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.

1 participant