Repository navigation
ci: setup release-please - #50
Conversation
Co-Authored-By: Claude Opus 5.5 (1M context) <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 52 minutes. View limit detailsLimit details: You’ve used the included review currently available. Review configuration: ⚙️ Run configuration
📒 Files selected for processing (1)
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (3)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughAdds Release Please configuration and version metadata for ChangesRelease automation
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Other Merge Risk: ⚪ Minimal · up to This change adds release automation for the 2.x branch and does not change runtime behavior. The risk of merging is minimal. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 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 |
release-please creates the 'autorelease: pending' label when it is missing. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Sets up release-please the same way as in roadrunner-api-dto:
.github/.release-please-config.json(bootstrap from the current2.xHEAD).github/version.jsonwith the current version.github/workflows/create-release.ymlrunning on2.xReleases will be created from conventional commits merged into
2.x.🤖 Generated with Claude Code
Summary by CodeRabbit