Skip to content

docs: correct base-foundryup default-version and release-title claims #48

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
amiecorso merged 1 commit into from
Jun 23, 2026
Merged

docs: correct base-foundryup default-version and release-title claims #48

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
11 changes: 7 additions & 4 deletions docs/base.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ installs the Base build under **namespaced commands**: `base-forge`, `base-cast`
`forge`/`cast`/`anvil`/`chisel`, is left completely untouched, so the two
toolchains coexist: keep using `forge` for everyday work, and reach for
`base-forge` only when you want Base precompile behavior. Re-run `base-foundryup`
any time to update.
any time to reinstall or change versions.

> `base-foundryup` and `foundryup` are independent: `base-foundryup` manages only
> the Base build and self-updates separately, so installing or updating Base
Expand All @@ -48,9 +48,12 @@ a specific Base release by name:
base-foundryup --install v1.1.0
```

With no version, `base-foundryup` installs the latest build. Each release on the
[releases page](https://github.com/base/base-anvil/releases) is titled with the
exact `base/base` commit it reproduces, and maintainer details live in
A bare `base-foundryup` installs the pinned default release (currently `v1.1.0`,
the latest stable Beryl build), not a rolling latest; nightlies are opt-in with
`base-foundryup --install nightly`. On the
[releases page](https://github.com/base/base-anvil/releases), versioned releases
are named for the Base version (e.g. `v1.1.0`) and nightlies are titled with the
`base/base` commit they reproduce. Maintainer details live in
[`RELEASES.md`](../RELEASES.md).

## Add the Base interfaces
Expand Down
Loading