Skip to content

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

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 19, 2026
Merged

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

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
34ad4fa
Drop foundry.toml release metadata: version intent lives in next-v ta…
thedavidmeister Aug 19, 2026
067f91e
Trim CLAUDE.md under the 4096-byte agent-context cap; correct stale r…
thedavidmeister Aug 19, 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
56 changes: 12 additions & 44 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,36 +24,11 @@ SPDX headers.

## Build & Test Commands

This project uses **Nix + Foundry (Forge)**. Enter the dev shell first:

```bash
nix develop
```

Then use rainix tasks:

```bash
# Static analysis (Slither)
nix develop -c rainix-sol-static

# License/legal checks (REUSE compliance)
nix develop -c rainix-sol-legal

# Prelude (dependency setup, run before other tasks)
nix develop -c rainix-sol-prelude

# Runs, but there is no test suite here: the interfaces have no behaviour to
# test. The tests that exercise them live in rain.factory.deploy, against the
# concrete.
nix develop -c rainix-sol-test
```

Direct Forge commands also work inside the nix shell:

```bash
# Build
forge build
```
Nix + Foundry. Enter the shell with `nix develop`, then run rainix tasks:
`rainix-sol-static` (Slither), `rainix-sol-legal` (REUSE), `rainix-sol-prelude`
(deps, run first), `rainix-sol-test`, and `forge build` directly. There is no
test suite here — the interfaces have no behaviour; the tests that exercise them
live in rain.factory.deploy against the concrete.

## Architecture

Expand Down Expand Up @@ -93,21 +68,14 @@ third-party library — which is what makes this half a standalone publish.

## Deployment

Nothing in this repo is deployed. The deterministic Zoltu deploy of the concrete
`CloneFactory`, its canonical address and codehash, and the deploy scripts
targeting Arbitrum, Base, Base Sepolia, Flare and Polygon are all in
Nothing here is deployed. The concrete `CloneFactory`, its address/codehash, and
the deploy scripts (Arbitrum, Base, Base Sepolia, Flare, Polygon) all live in
rain.factory.deploy.

## Releases

Library repo, so `package-release.yaml` runs `rainix-autopublish`:
`[package].version` in `foundry.toml` is the NEXT, unpublished version, and a
content change on merge publishes it and bumps to the next. Nothing here is
tag-released, and no snapshot is frozen — that lifecycle belongs to the deploy
half.

## CI

GitHub Actions runs three parallel jobs on every push: `rainix-sol-test`,
`rainix-sol-static`, `rainix-sol-legal`. There are no fork tests and no RPC
secrets are needed.
Library repo: `package-release.yaml` runs `rainix-autopublish`. A content change
on merge publishes to Soldeer at a registry-derived version (newest published,
patch-bumped); push a `next-v<x.y.z>` tag on main to jump minor/major.
`foundry.toml` holds no release metadata, nothing is committed back, and no
snapshot is frozen — that lifecycle belongs to the deploy half.
4 changes: 0 additions & 4 deletions foundry.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,3 @@
[package]
name = "rain-factory"
version = "0.1.7"

[profile.default]
src = 'src'
test = 'test'
Expand Down
Loading