Drop foundry.toml release metadata: version intent lives in next-v tags (rainix#335)

[thedavidmeister]

Deletes the legacy [package] release-metadata section (name/version) from foundry.toml, per the ruling in rainlanguage/rainix#335. Since rainlanguage/rainix#336 merged, rainix-autopublish derives the publish version from the Soldeer registry plus next-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

• Discriminating tests: n/a - config-metadata deletion; nothing reads the section since rainix#336. Verified locally: nix develop -c reuse lint, nix develop -c forge soldeer install, and the full nix develop -c forge test suite all green.
• Mutations applied: n/a - no code changed
• Oracle: rainix#336 gate semantics (section excluded from content hash; version from registry + next-v tags)
• Category check: issue asks removal of release metadata from consumers; covered exactly for this repo

Summary by CodeRabbit

• Chores
  • Simplified project configuration by removing package metadata.
  • Existing build, compiler, optimization, dependency, and package-management settings remain unchanged.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 34f11fe0-e52e-4fa3-b9d3-a71b4fb80c6f

📥 Commits

Reviewing files that changed from the base of the PR and between a4692fd and 7a81840.

📒 Files selected for processing (1)

• foundry.toml

💤 Files with no reviewable changes (1)

• foundry.toml

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

Walkthrough

Removed the [package] metadata block from foundry.toml. Foundry profiles, compiler, optimizer, dependency, and Soldeer settings remain unchanged.

Changes

Cohort / File(s)	Summary
Foundry configuration foundry.toml	Removes the package name and version metadata.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 7a818

This change removes unused release metadata from foundry.toml without changing product code or release behavior. The supplied validation is green, and no actionable merge-blocking risk remains beyond normal checks and review.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the removal of release metadata from foundry.toml and states the replacement version source.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 2026-08-19-drop-release-metadata

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}