Skip to content

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

Open
thedavidmeister wants to merge 1 commit into
mainfrom
2026-08-19-drop-release-metadata
Open

Drop foundry.toml release metadata: version intent lives in next-v tags (rainix#335)#336
thedavidmeister wants to merge 1 commit into
mainfrom
2026-08-19-drop-release-metadata

Conversation

@thedavidmeister

@thedavidmeister thedavidmeister commented Aug 19, 2026

Copy link
Copy Markdown
Collaborator

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 test: 405 passed locally, and the 1 fork test needing ARBITRUM_RPC_URL passed on rerun against a public endpoint; 0 failures attributable to this change)
  • 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.

…gs (rainix#335)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@thedavidmeister thedavidmeister self-assigned this Aug 19, 2026
@coderabbitai

coderabbitai Bot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

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: 553b323d-3896-46a1-b5d5-a7e67d3780ef

📥 Commits

Reviewing files that changed from the base of the PR and between 242dd24 and 1b65570.

📒 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] metadata block from foundry.toml, including the package name and version.

Changes

Cohort / File(s) Summary
Package metadata
foundry.toml
Removes the rain-vats package name and version declarations.

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

Merge Risk: ⚪ Minimal · up to 1b655

This is a localized removal of unused release metadata in foundry.toml; it should not change publishing or runtime behavior, so 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 describes the removal of release metadata and states where version intent now lives.
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

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant