Autopublish to Soldeer on merge to main#318
Conversation
Add package-release.yaml calling the rainix-autopublish reusable with soldeer-package: rain-vats, and a [package] version in foundry.toml (the version source the reusable reads). On merge to main, autopublish publishes to Soldeer whenever foundry.toml's version diverges from the registry — replacing the manual v* tag flow, so publish-soldeer.yaml is removed. Set version 0.1.6 to publish the #309 fix. Depends on rainlanguage/rainix#215 (soldeer-only support in the reusable). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
… version Completes the previous commit (which only removed publish-soldeer.yaml): the new package-release.yaml calls the rainix-autopublish reusable with soldeer-package: rain-vats, and foundry.toml gets a [package] version (0.1.6) as the version source the reusable reads. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 55 minutes and 36 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 |
Review verdict: APPROVEReviewed e2f2ced CI green (legal/static/test + CodeRabbit). Reviewed the diff at head
rainix#215 is merged, so the reusable's soldeer-only path is live. Merging this triggers the autopublish → publishes Verdict: approve. Merging. |
What
Wire rain.vats to auto-publish to Soldeer on merge to
main, instead of the manualv*tag flow.package-release.yaml— calls therainix-autopublish.yamlreusable withsoldeer-package: rain-vatson push tomain. The reusable reads the version fromfoundry.toml, compares it to the Soldeer registry, andforge soldeer pushes when they diverge (no auto-bump — the version is set explicitly here).foundry.toml— adds a[package]version(the source the reusable reads). Set to0.1.6to publish the H01 - ERC1155 Acceptance Callback Enables Persistent Operator Approval Via _msgSender Spoofing #309_msgSenderspoof fix (registry is currently0.1.5). Foundry tolerates the[package]section (emits only an "unknown config section" warning;forge config/build/test still parse it).publish-soldeer.yamlremoved — the tag-triggered flow is superseded by autopublish.Ordering
Depends on rainlanguage/rainix#215 (soldeer-only support in the reusable — without it the reusable's
Resolve cratesstep fails for a crate-less repo). Merge #215 first; then merging this PR triggers the autopublish and publishesrain-vats~0.1.6.Going forward
Bump
[package].versioninfoundry.tomlin the PR that should ship a new Soldeer release; the merge tomainpublishes it automatically.🤖 Generated with Claude Code