From 30b26e2eca5639be266d405645c0bcc19a28ab12 Mon Sep 17 00:00:00 2001 From: David Meister Date: Wed, 19 Aug 2026 17:55:40 +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 | 10 +++++----- foundry.toml | 8 -------- 2 files changed, 5 insertions(+), 13 deletions(-) diff --git a/README.md b/README.md index a40712a..1d14f5d 100644 --- a/README.md +++ b/README.md @@ -115,12 +115,12 @@ Publishing is merge-driven; there is no release tag to push. On every push to `main`, [`Package Release`](.github/workflows/package-release.yaml) calls rainix's `rainix-autopublish`, which compares the package content against the latest published revision. If it differs, it runs -`forge soldeer push rain-solmem~`, tags `sol-v`, and commits a -bump of `[package] version` back to `main`. +`forge soldeer push rain-solmem~` and tags `sol-v`. -`[package] version` in `foundry.toml` is the **next, unpublished** version, not -the current one. It is always one ahead of the registry; do not "correct" it to -match. +The publish version is derived from the Soldeer registry and git tags, never +from `foundry.toml`: it is the semver max of a patch bump of the newest +published version and the newest `next-v` tag merged into the pushed +head. Push a `next-v` tag to request a deliberate minor or major jump. Everything [`.soldeerignore`](.soldeerignore) does not exclude ships — `src/**`, `README.md`, `LICENSE`, `LICENSES/`, `REUSE.toml` — and any change to it diff --git a/foundry.toml b/foundry.toml index e8de1cc..a42a6b5 100644 --- a/foundry.toml +++ b/foundry.toml @@ -1,11 +1,3 @@ -# Release metadata, not foundry config. `rainix-autopublish` reads `version` as -# the next, unpublished Soldeer release and rewrites it when it publishes. -# `[external.*]` is the section foundry reserves for another tool's config and -# ignores; any other unreserved section it reads as a profile and warns about. -[external.package] -name = "rain-solmem" -version = "0.1.27" - [profile.default] # See more config options https://github.com/foundry-rs/foundry/tree/master/config From 507762fc4df4f5ba8e89d9ec0b4f794e2a79c987 Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 25 Aug 2026 17:47:15 +0000 Subject: [PATCH 2/2] Clarify that next-v tags are read only on pushes to main 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 1d14f5d..08c8b9b 100644 --- a/README.md +++ b/README.md @@ -120,7 +120,7 @@ latest published revision. If it differs, it runs The publish version is derived from the Soldeer registry and git tags, never from `foundry.toml`: it is the semver max of a patch bump of the newest published version and the newest `next-v` tag merged into the pushed -head. Push a `next-v` tag to request a deliberate minor or major jump. +head. Push a `next-v` tag to request a deliberate minor or major jump; the tag is read only when a push to `main` runs the workflow, so it must already be merged into the pushed head — a tag-only push publishes nothing. Everything [`.soldeerignore`](.soldeerignore) does not exclude ships — `src/**`, `README.md`, `LICENSE`, `LICENSES/`, `REUSE.toml` — and any change to it