Drop foundry.toml release metadata: version intent lives in next-v tags (rainix#335) - #39
Drop foundry.toml release metadata: version intent lives in next-v tags (rainix#335)#39thedavidmeister 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 ChangesRelease metadata
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This is a localized removal of obsolete release metadata with no actionable merge-blocking risk remaining 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 |
Drops the
[external.package]release-metadata section (and its attached comment block) from foundry.toml, per the ruling on rainlanguage/rainix#335. Since rainlanguage/rainix#336 merged, rainix-autopublish derives the publish version from the Soldeer registry +next-v*git tags and never reads this section, and the publish gate excludes the section (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. Verified locally:nix develop -c reuse lint(compliant),forge soldeer installandforge test(8 passed, 0 failed).QA
nix develop -c forge test: 8 passed, 0 failed;reuse lintcompliant)Summary by CodeRabbit