ci: set up soldeer autopublish for rain-pyth#24
Conversation
Now that rain.pyth is de-submoduled (#23) it can be published to soldeer. Add [package] (name=rain-pyth, version=0.1.0 first release) + a rainix-autopublish wrapper (soldeer-package: rain-pyth). Towards #22. NB: the rain-pyth project must be created on soldeer.xyz before the first push succeeds (the registry rejects pushes to a nonexistent project).
|
Warning Review limit reached
More reviews will be available in 13 minutes and 40 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 (2)
✨ 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 |
Towards #22 — publish rain.pyth to the soldeer registry.
Now that rain.pyth is de-submoduled (#23 merged), it can be published. This wires it up:
[package](name = "rain-pyth",version = "0.1.0"— first release; no prior tags/registry entry) tofoundry.toml.package-release.yamlcallingrainix-autopublish(soldeer-package: rain-pyth), which publishesrain-pyth~<version>on push to main when the foundry.toml version diverges from the registry.rain-pythproject must be created on soldeer.xyz before the first push succeeds — the registry rejects pushes to a nonexistent project, and the workflow does not create it. After this PR merges, thepackage-releasejob will attemptrain-pyth~0.1.0and fail until the project exists; once created, re-run (or next push) publishes and #22 can close.