From 3198616ad6fa0c2048d31a2a26eb73eb5f375b28 Mon Sep 17 00:00:00 2001 From: David Meister Date: Wed, 19 Aug 2026 17:50:57 +0000 Subject: [PATCH 1/2] Drop foundry.toml release metadata: version intent lives in next-v tags (rainix#335) Co-Authored-By: Claude Fable 5 --- README.md | 4 ++-- foundry.toml | 10 ---------- 2 files changed, 2 insertions(+), 12 deletions(-) diff --git a/README.md b/README.md index 56ad344..a0a7593 100644 --- a/README.md +++ b/README.md @@ -146,8 +146,8 @@ reusable on every push to `main`, passing the package name explicitly as `soldeer-package: rain-sol-codegen`. That workflow owns both the version and the release tag, so neither is set by -hand. `[external.package].version` in `foundry.toml` is therefore the next, -unpublished version rather than the last published one. +hand. The next version is derived from the Soldeer registry and `next-v*` git +tags, so no version is recorded in this repo's files. ## License diff --git a/foundry.toml b/foundry.toml index afd2488..2cb1fbf 100644 --- a/foundry.toml +++ b/foundry.toml @@ -1,13 +1,3 @@ -# Release metadata, not foundry config: `rainix-autopublish` reads `version` as -# the next, unpublished Soldeer release and rewrites it when it publishes, and -# neither forge nor soldeer reads anything here. `[external.*]` is the section -# foundry reserves for another tool's config and ignores; a section it does not -# reserve is read as a profile, which it warns about on every invocation and -# `forge config --fix` rewrites into `[profile.*]`. -[external.package] -name = "rain-sol-codegen" -version = "0.1.37" - [profile.default] src = 'src' out = 'out' From 9ca2a81e4e580b05812963883e487b3136e9c6d9 Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 25 Aug 2026 17:20:37 +0000 Subject: [PATCH 2/2] Clarify that only the package release version is unrecorded Co-Authored-By: Claude Fable 5 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index a0a7593..de29235 100644 --- a/README.md +++ b/README.md @@ -147,7 +147,7 @@ reusable on every push to `main`, passing the package name explicitly as That workflow owns both the version and the release tag, so neither is set by hand. The next version is derived from the Soldeer registry and `next-v*` git -tags, so no version is recorded in this repo's files. +tags, so this repo's own release version is not recorded in its files (dependency versions still live in `soldeer.lock`). ## License