docs: add v1.2.0-rc.2 pre-release docs#792
Merged
Merged
Conversation
Contributor
|
Warning Review limit reached
Next review available in: 55 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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (180)
📒 Files selected for processing (3)
📝 WalkthroughWalkthroughAdds v1.2.0-rc.2 to Docusaurus version configuration and the versions list, and records the release in the documentation changelog. ChangesDocumentation release version
Estimated code review effort: 1 (Trivial) | ~3 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ 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 |
Snapshot current docs as opt-in v1.2.0-rc.2 version (non-default, noIndex, unreleased banner) alongside v1.2.0-rc.1 and v1.2.0-m.1; keep v1.1.x as lastVersion. Point githubRef at the release-v1.2.0-rc.2 branch since it already exists, and add the v1.2.0-rc.2 row to the changelog, comparing against v1.2.0-rc.1. Signed-off-by: Mevan <mevan.karu@gmail.com>
VajiraPrabuddhaka
approved these changes
Jul 24, 2026
LakshanSS
approved these changes
Jul 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Snapshot current docs as opt-in v1.2.0-rc.2 version (non-default, noIndex, unreleased banner) alongside v1.2.0-rc.1 and v1.2.0-m.1; keep v1.1.x as lastVersion. Point githubRef at the release-v1.2.0-rc.2 branch since it already exists, and add the v1.2.0-rc.2 row to the changelog, comparing against v1.2.0-rc.1.