docs: cover Foundry v1.7 Tempo, MPP, and selective follow-up gaps#1803
Merged
zerosnacks merged 4 commits intomasterfrom Apr 30, 2026
Merged
docs: cover Foundry v1.7 Tempo, MPP, and selective follow-up gaps#1803zerosnacks merged 4 commits intomasterfrom
zerosnacks merged 4 commits intomasterfrom
Conversation
Amp-Thread-ID: https://ampcode.com/threads/T-019ddd34-8a73-719d-ab58-e7364f20d712 Co-authored-by: Amp <amp@ampcode.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Amp-Thread-ID: https://ampcode.com/threads/T-019ddd34-8a73-719d-ab58-e7364f20d712 Co-authored-by: Amp <amp@ampcode.com>
Member
|
cc @mablr / @figtracer please have a look |
Amp-Thread-ID: https://ampcode.com/threads/T-019dddff-1855-752f-b136-bd0465462ac8 Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019dddff-1855-752f-b136-bd0465462ac8 Co-authored-by: Amp <amp@ampcode.com>
mablr
reviewed
Apr 30, 2026
Contributor
mablr
left a comment
There was a problem hiding this comment.
Sgtm.
We will need to include per-test network selection logic foundry-rs/foundry#14530.
Member
Sounds good, lets do that as a follow up |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR documents the most important user-facing gaps I found while reviewing the Foundry v1.7.0 release notes against the current book, with a focus on Tempo and MPP first, plus a small selective follow-up for other high-leverage v1.7.0 features.
This PR now:
foundryup -n tempoinstall flow with upstream v1.7.0 guidanceforge init --network tempo,foundry.tomlsetup, Tempo transaction flags, and Anvil usage402-gated RPCs, key discovery, deposit tuning, and channel persistencenetworkand namespacedhardforkconfig in the config reference and default config pageforge inspect ... linearizationScope
I kept this intentionally selective.
The release notes contain many v1.7.0 changes that are already discoverable through generated CLI reference pages or are too narrow to justify guide-level documentation right now. This PR focuses on the user-facing gaps that were both:
Audit Findings
The main gaps I found were:
networkkey or namespaced runtimehardforkvalues liketempo:T3402handlingforge inspect ... linearizationReferences
Validation
NODE_OPTIONS='--max-old-space-size=4096' ./node_modules/.bin/vite build