Drop foundry.toml release metadata: version intent lives in next-v tags (rainix#335) - #336
Drop foundry.toml release metadata: version intent lives in next-v tags (rainix#335)#336thedavidmeister wants to merge 1 commit into
Conversation
…gs (rainix#335) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe change removes the Changes
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This is a localized removal of unused release metadata in foundry.toml; it should not change publishing or runtime behavior, so no actionable merge-blocking risk remains beyond normal checks and review. 🚥 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 |
Deletes the foundry.toml release-metadata section per rainlanguage/rainix#335. Since rainlanguage/rainix#336 merged, rainix-autopublish derives the publish version from the Soldeer registry plus
next-v*git tags; the section is never read, and the autopublish content gate excludes it (including its attached comment block) from the content hash, so this deletion is content-neutral: it cannot mint a spurious release and changes no behavior.QA
nix develop -c reuse lintgreen;forge soldeer install+forge test: 405 passed locally, and the 1 fork test needing ARBITRUM_RPC_URL passed on rerun against a public endpoint; 0 failures attributable to this change)Summary by CodeRabbit