Release version 0.1.8 - #23
Conversation
rainix-tag-release's guard requires the committed [external.package] version to match the pushed tag. sol-v0.1.7 was tagged before this rule was known here and its guard run rejected the mismatch against 0.1.5; that tag stays as a dead marker and this release is 0.1.8 (the rain-factory-deploy version space is empty, so nothing is skipped). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 23 minutes Limit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?Wait for the limit to reset, then comment An organization admin can change what happens after included review limits in Billing. How do review limits work?CodeRabbit enforces per-developer PR review limits within each organization. For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
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 |
The sol-v0.1.7 release run failed at rainix-tag-release's release-guard: the committed
[external.package]version (0.1.5) must match the pushed tag. This bumps the version to 0.1.8 so the release ships as sol-v0.1.8 tagged at this commit; sol-v0.1.7 stays as a dead marker (tag deletion is out of scope for this session's tooling), and the rain-factory-deploy version space is empty so no number is skipped.QA
🤖 Generated with Claude Code