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

[thedavidmeister]

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

• Discriminating tests: n/a - config-metadata deletion; nothing reads the section since rainix#336 (local nix develop -c reuse lint green; forge soldeer install + forge build successful; the repo has no forge tests on main (forge test finds none))
• 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
  • Removed package metadata from the project configuration.
  • Existing compiler, dependency, profile, and fuzzing 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: 588382c8-e709-43a5-8f41-ed3694a64a54

📥 Commits

Reviewing files that changed from the base of the PR and between 45348d3 and 8ff1d49.

📒 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 profile, compiler, dependency, and fuzzing 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 8ff1d

This localized configuration cleanup removes obsolete release metadata without changing publishing behavior or release-version selection; no actionable merge-blocking risk remains after 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.}