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 nix develop -c forge build green. This repo has no test/ directory, so the build is the full local check; CI runs its own pipeline.
• 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 name and version metadata from the project configuration.
  • All compiler, testing, dependency, and build settings remain unchanged.

[coderabbitai]

Warning

Review limit reached

@thedavidmeister, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 9 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: d6e5032c-fc22-4a06-ad05-d222af1a0ba6

📥 Commits

Reviewing files that changed from the base of the PR and between 34ad4fa and 067f91e.

📒 Files selected for processing (1)

• CLAUDE.md

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: 619f045d-015b-4158-8e66-dd0ebb541c19

📥 Commits

Reviewing files that changed from the base of the PR and between 1b6adb9 and 34ad4fa.

📒 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

The change removes the [package] section from foundry.toml, including the project name and version. Other Foundry configuration remains unchanged.

Changes

Foundry configuration

Layer / File(s)	Summary
Remove package metadata foundry.toml	Removes the rain-factory package name and 0.1.7 version declarations.

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

Merge Risk: ⚪ Minimal · up to 34ad4

This localized configuration cleanup removes obsolete release metadata without changing application behavior; 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 and concisely describes the removal of release metadata from foundry.toml and the use of next-v tags for version intent.
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 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 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.}