docs(release): name 2.1.0-rc.2 as the promoted 2.1.0 candidate - #437
Conversation
README.md and the docs roadmap said v2.1.0 promotes rc.1 unchanged, but rc.1's GitHub publish failed on the release-body byte limit (fixed in PR #429), so rc.2 was the candidate actually promoted; the GA tree matches rc.2, not rc.1. Matches CHANGELOG.md's existing [2.1.0] wording.
|
@coderabbitai review |
|
Deployment failed for project sockguard-website with the following error: Learn More: https://vercel.com/codeswhat?upgradeToPro=build-rate-limit |
|
|
Important Review skippedNo new commits to review since the last review. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Team Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Team Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughUpdated the README release notes and roadmap to reference Merge Risk: ⚪ Minimal · up to This updates README and roadmap release references to identify 2.1.0-rc.2 as the candidate promoted to v2.1.0. The documentation changes are consistent and present no remaining merge-readiness risk. 🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 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 |
|
@coderabbitai review |
|
|
@coderabbitai review |
|
|
@coderabbitai review |
|
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
@coderabbitai review |
|
|
@coderabbitai review |
|
biggest-littlest
left a comment
There was a problem hiding this comment.
Reviewed against the CHANGELOG entry and the diff; CI green outside the qlty/Vercel quota noise.
ALARGECOMPANY
left a comment
There was a problem hiding this comment.
Reviewed against the CHANGELOG entry and the diff; CI green outside the qlty/Vercel quota noise.
README.md and the docs roadmap said v2.1.0 promotes
2.1.0-rc.1unchanged. rc.1's GitHub publish failed on the release-body byte limit (#429), so rc.2 was the candidate actually promoted and the GA tree matches rc.2. Both pages now say rc.2, matching what CHANGELOG.md's[2.1.0]entry already says.Docs only. CHANGELOG has a
### Documentationline under Unreleased.Changelog
🔧 Changed
README.mdto identify2.1.0-rc.2as the promotedv2.1.0candidate.docs/content/docs/roadmap.mdxto identify2.1.0-rc.2as the stable release candidate.