From a87eafc785fac35108706c66e959e2fef0865347 Mon Sep 17 00:00:00 2001 From: David Meister Date: Sat, 15 Aug 2026 07:42:04 +0000 Subject: [PATCH] Remove submodule-era residue from .soldeerignore MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit `.soldeerignore` is a publish filter, not a description of the tree, so an entry naming a file that is absent today is normally a forward-looking rule worth keeping. These three are not: they are tied to a dependency mechanism this repo no longer uses and cannot go back to. - `.gitmodules` and `/lib` are the git-submodule vendoring layout. Rainix CI runs a `no-submodules` check that fails on a root `.gitmodules` or any committed gitlink, so no future commit can reintroduce either path for these entries to filter. - `/foundry.lock` is Foundry's git-submodule lockfile — it pins the commit of each dependency vendored under `lib/` so `forge install` / `forge update` can restore identical revisions. It is only meaningful alongside that same banned layout. `soldeer.lock` is the live lockfile here and everything lands under `dependencies/`, because `foundry.toml` sets `libs = ['dependencies']`. Every other entry is left alone, including the ones absent from a clean checkout by design (`.DS_Store`, `/deployments`) — those are OS junk and build output that IS present when `soldeer push` runs, so they still filter. `forge soldeer push --dry-run` packs a byte-identical 525-entry set before and after this change. Closes #553 Co-Authored-By: Claude Opus 5 (1M context) --- .soldeerignore | 3 --- 1 file changed, 3 deletions(-) diff --git a/.soldeerignore b/.soldeerignore index ad1586c48..afe569ebc 100644 --- a/.soldeerignore +++ b/.soldeerignore @@ -7,7 +7,6 @@ .git .github .gitignore -.gitmodules .pre-commit-config.yaml .prettierignore .soldeerignore @@ -18,9 +17,7 @@ CLAUDE.md /dependencies /flake.lock /flake.nix -/foundry.lock /foundry.toml -/lib /out /remappings.txt /slither.config.json