Repository navigation
quest: apply maintainer fixes to merged quest plans - #6385
Conversation
- Delete jitter-density; #6359 bounded the jitter reference history. - announce-cursor-cpu, max-hops-setting, and drain-peer-redial ship with the next cut from main instead of a release backport. - Drop the release-audit child count so it cannot go stale. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 35 minutes. View limit details
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 |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Maintainer-approved quest fixes for PRs that merged before they could be applied on their branches.
quest/m1/jitter-density.mdand its links, since moq-dev/moq#6359 already bounded the jitter reference history.announce-cursor-cpu,max-hops-setting, anddrain-peer-redialare not backported torelease; they ship with the next cut frommain.Public API: none. Wire: none.
quest checkpasses.(Written by Claude Opus 5.5)
🤖 Generated with Claude Code