Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
thedavidmeister merged 2 commits into from
Aug 25, 2026
Merged

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

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
30b26e2
Drop foundry.toml release metadata: version intent lives in next-v ta…
thedavidmeister Aug 19, 2026
507762f
Clarify that next-v tags are read only on pushes to main
claude Aug 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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~<version>`, tags `sol-v<version>`, and commits a
bump of `[package] version` back to `main`.
`forge soldeer push rain-solmem~<version>` and tags `sol-v<version>`.

`[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<x.y.z>` tag merged into the pushed
head. Push a `next-v<x.y.z>` 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
Expand Down
8 changes: 0 additions & 8 deletions foundry.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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
Expand Down
Loading