Skip to content

chore(main): release 0.2.3#7

Open
jmagar wants to merge 1 commit into
mainfrom
release-please--branches--main--components--unraid-rmcp
Open

chore(main): release 0.2.3#7
jmagar wants to merge 1 commit into
mainfrom
release-please--branches--main--components--unraid-rmcp

Conversation

@jmagar

@jmagar jmagar commented Jul 12, 2026

Copy link
Copy Markdown
Collaborator

This release PR is managed by release-please. Merge it to let release-please create the tag and GitHub Release.

0.2.3 (2026-07-23)

Fixed

  • accept numeric BigInt responses (a377767)
  • deploy from renamed runraid image (92176cb)
  • route rust builds through sccache wrapper (be6b2ab)

After release-please publishes the GitHub Release, release.yml builds and attaches the linux/amd64 binary and Docker image.

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@coderabbitai

coderabbitai Bot commented Jul 12, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 4 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: ASSERTIVE

Plan: Pro

Run ID: 476e1ecc-dc50-4818-b60c-71e37f73eee2

📥 Commits

Reviewing files that changed from the base of the PR and between 5f80350 and fbf7247.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock and included by **/*
📒 Files selected for processing (4)
  • .release-please-manifest.json
  • CHANGELOG.md
  • Cargo.toml
  • xtask/Cargo.toml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release-please--branches--main--components--unraid-rmcp

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.

@jmagar
jmagar force-pushed the release-please--branches--main--components--unraid-rmcp branch 5 times, most recently from 42a7a19 to fbf7247 Compare July 19, 2026 23:53
@jmagar
jmagar force-pushed the release-please--branches--main--components--unraid-rmcp branch from fbf7247 to 94ab06c Compare July 23, 2026 20:22
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