ci: migrate soldeer publishing to rainix-autopublish#8
Conversation
Replace tag-driven publish-soldeer with rainix-autopublish (version-divergence on push to main). Add [package].version = 0.1.0 (current registry release).
|
Warning Review limit reached
More reviews will be available in 55 minutes and 54 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ 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 |
|
Reviewed 0f95f82: APPROVE — migrate soldeer publishing to rainix-autopublish. Adds [package].version=0.1.0 (current registry release, no publish fires), swaps publish-soldeer for the autopublish wrapper (soldeer-package: rain-verify-interface). Checks green. |
Part of removing the manual
publish-soldeerreusable from rainix. Adds[package].version = 0.1.0(current registry release) to foundry.toml, replaces the tag-driven wrapper withrainix-autopublish(soldeer-package: rain-verify-interface). Release model: tag → bump version + merge to main. No publish fires from this PR.