foundry-nightly: init at nightly-2026-02-16

[aldoborrero]

Summary

• Add foundry-nightly package tracking the nightly release channel
• Based on nightly-f8e3dfaf9a6eb88481c095bf7bf5286b3c5d0b4a (2026-02-16)
• Includes fully automated update.py script for CI updates

Differences from stable foundry

• Tracks nightly releases instead of stable tags
• Uses VERGEN_GIT_SHA and VERGEN_IDEMPOTENT env vars to provide version info (no .git directory in source)
• Custom update.py that automatically computes hashes

Update workflow

The update.py script is fully automated and CI-compatible:

./packages/foundry-nightly/update.py

It will:

1. Check for new nightly release via GitHub API
2. Update svm-lists (solc binary lists)
3. Automatically compute source hash
4. Automatically compute cargo hash
5. Update package.nix with all values

Test plan

• Build completes: nix build .#foundry-nightly
• Binaries work: forge --version, cast --version, anvil --version
• Update script tested: downgraded to older nightly, ran script, hashes auto-computed
• CI verification

[bbjubjub2494]

a consideration: given that foundry takes a long time to build, are we adding significant daily load on buildbot? If so is it proportional to the benefit?

[bbjubjub2494]

is this intentional?

[aldoborrero]

No at all (claude hallucination and a oversight on my part)!

[aldoborrero]

Not at all then, it was just copied from the original foundry recipe, which contains that author :)

[aldoborrero]

Maybe better to remove the author field

[aldoborrero]

a consideration: given that foundry takes a long time to build, are we adding significant daily load on buildbot? If so is it proportional to the benefit?

Good question. I've occasionally needed nightly builds myself. That alone doesn't justify this, but I was also thinking about the foundry.nix repo — with this option, we'd also eliminate the need for users to use that as well, concentrating it on ethereum.nix.

[aldoborrero]

Once #936 is merged I'll rebase it and I'll use it on this PR.