ci(research): pin the Rustfmt patch release - #134
Conversation
|
Warning Review limit reached
Next review available in: 31 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 18e1fb74cd
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Change contract
Pin Prediction Markets CI formatting to Rustfmt 1.91.0 so the repository is checked against the exact formatter version its checked-in sources already satisfy, instead of drifting when a new 1.91 patch is published.
Out of scope
Formatting source files, changing any Rust behavior, changing other CI lanes, or upgrading the toolchain.
Dependency or merge order
None. Merge before rerunning PR #133, whose formatter failure is caused by 1.91.1 reformatting unrelated root-workspace files.
Focused validation
GitHub Linux run 29645348606 checked current main with Rustfmt 1.91.0 using the same cargo fmt --all -- --check command and passed. The failing PR #133 lane resolved toolchain 1.91.1 and reported only unrelated root-workspace formatting drift.
Rollout or rollback impact
CI-only. Rollback is a one-line revert; no runtime or live execution impact.