docs(security): roll the support window to 2.1.x and 2.0.x - #431
Conversation
v2.1.0 is out, so under the stated two-minor window 1.7.x leaves support. No 1.x maintenance branch remains.
|
@coderabbitai review |
|
Deployment failed for project sockguard-website with the following error: Learn More: https://vercel.com/codeswhat?upgradeToPro=build-rate-limit |
|
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 selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe security support matrix now lists Merge Risk: ⚪ Minimal · up to The security-support documentation now lists 2.1.x and 2.0.x as supported and retires older lines. No current merge-blocking risk remains. 🚥 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 |
|
biggest-littlest
left a comment
There was a problem hiding this comment.
Support table follows the stated two-minor window now that 2.1.0 is out.
ALARGECOMPANY
left a comment
There was a problem hiding this comment.
Support table follows the stated two-minor window now that 2.1.0 is out.
v2.1.0 shipped, so under the two-minor window in SECURITY.md the supported lines are 2.1.x and 2.0.x and 1.7.x drops off. The table follows the policy that's already written above it. The 1.6.x maintenance branch is retired too; its tip is kept as the
archive/maintenance-1.6.xtag.Changelog
🔒 Security
SECURITY.mdto support2.1.xand2.0.x.1.7.xas unsupported.1.6.xmaintenance branch.1.6.xtip underarchive/maintenance-1.6.x.