Drop foundry.toml release metadata: version intent lives in next-v tags (rainix#335) - #25
Drop foundry.toml release metadata: version intent lives in next-v tags (rainix#335)#25thedavidmeister 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 localized configuration cleanup removes obsolete release metadata without changing runtime behavior; no actionable merge-blocking risk remains after 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 legacy
[package]release-metadata section (name/version) fromfoundry.toml, per the ruling in rainlanguage/rainix#335. Since rainlanguage/rainix#336 merged,rainix-autopublishderives the publish version from the Soldeer registry plusnext-v*git tags and never reads this section; the publish gate also excludes the section from the content hash, so this deletion is content-neutral and cannot mint a release.QA
nix develop -c reuse lint,nix develop -c forge soldeer install, and the fullnix develop -c forge testsuite all green.Summary by CodeRabbit