-
Notifications
You must be signed in to change notification settings - Fork 233
docs: fix readme post 0.5 #1858
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
fixed a typo : Features Coming soon to 0.6 Signed-off-by: Ashwath Aithal <[email protected]>
📝 WalkthroughWalkthroughUpdated README.md with version bump from v0.4 to v0.6 and expanded the Features section with new entries including improved performance optimizations, new model support (Qwen3-Next, Nemotron-Super), additional algorithms (GDPO, LoRA, GRPO, DPO), resiliency features, on-policy distillation, and speculative decoding. Changes
Possibly related PRs
Suggested labels
Suggested reviewers
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 3 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (3 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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
README.md (1)
86-86:⚠️ Potential issue | 🟡 MinorFix typo: "Speculaive" should be "Speculative".
The word "Speculaive" is misspelled and should be "Speculative".
📝 Proposed fix
-- 🔜 **Speculaive Decoding** - Speculative Decoding support for rollout acceleration +- 🔜 **Speculative Decoding** - Speculative Decoding support for rollout acceleration
🤖 Fix all issues with AI agents
In `@README.md`:
- Line 76: The PR description incorrectly calls this a "typographical issue"
while the diff actually changes the release indicator from v0.4 to v0.6 (the
line "✅ _Available now_ | 🔜 _Coming in v0.6_"); update the PR description/title
to accurately state this is a semantic version bump and include a brief
justification of why the release timeline changed, mention any user-impacting
changes tied to the bump, and update related metadata (release notes/changelog)
to reflect v0.6 rather than a typo fix.
fixed a typo : Features Coming soon to 0.6
What does this PR do ?
Add a one line overview of what this PR aims to accomplish.
Issues
List issues that this PR closes (syntax):
Usage
# Add a code snippet demonstrating how to use thisBefore your PR is "Ready for review"
Pre checks:
Additional Information
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.