You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore: backport: fix(aztec-up): installer does not shadow user binaries on PATH (#22902) (#23060)
Backport of #22902 to `backport-to-v4-next-staging`.
## Original change
Native binaries (`forge`, `nargo`, `anvil`, `bb`, …) now live in
`~/.aztec/current/internal-bin` (off `PATH`) and are exposed only via
`aztec-<tool>` symlinks in `~/.aztec/current/bin`. The `aztec`
entrypoint prepends `internal-bin` to its child `PATH` so workflows that
cross-call by basename keep working without leaking those names to the
user's shell.
## Cherry-pick conflict
One conflict during cherry-pick:
- `docs/docs-developers/docs/tutorials/js_tutorials/aave_bridge.md` —
*deleted by us, modified by them.* The file no longer exists on
`backport-to-v4-next-staging`, so the upstream modification has nothing
to apply against.
**Resolution:** dropped the file (matches v4-next state). The first
commit preserves the original cherry-pick result (file restored as
upstream had it) so reviewers can see what would have landed; the second
commit removes it.
No build fixes were needed — the change touches only shell installer
scripts, a standalone TS acceptance test, and docs. Shell syntax checked
with `bash -n` for all modified scripts.
## Commits
1. `fix(aztec-up): ...` — original cherry-pick result, including the
unresolvable file.
2. `fix: resolve cherry-pick conflicts` — drop `aave_bridge.md` to match
the target branch.
ClaudeBox log: https://claudebox.work/s/a57acc5286aef8a6?run=1
Copy file name to clipboardExpand all lines: aztec-up/README.md
+8-3Lines changed: 8 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,9 +9,14 @@ That is all.
9
9
This will install into `~/.aztec/bin` a collection of scripts to help with running aztec containers, and will update
10
10
the user's `PATH` variable in their shell startup script so they can be found.
11
11
12
-
-`aztec` - a collection of tools to compile and test contracts, to launch subsystems and interact with the aztec network."
13
-
-`aztec-up` - a tool to install and manage aztec toolchain versions."
14
-
-`aztec-wallet` - our minimalistic CLI wallet"
12
+
-`aztec` - compiles and tests contracts, launches infrastructure subsystems, interacts with the network.
13
+
-`aztec-up` - a version manager for the Aztec toolchain.
14
+
-`aztec-wallet` - a tool for interacting with the Aztec network.
15
+
-`aztec-bb` - the Barretenberg proving backend.
16
+
-`aztec-nargo` - the Noir compiler and simulator.
17
+
-`aztec-forge`, `aztec-cast`, `aztec-anvil`, `aztec-chisel` - the bundled Foundry tools.
18
+
19
+
Foundry, Noir, and Barretenberg are bundled at the versions `aztec` needs. Your own `forge` / `nargo` / `bb` installs still work under their bare names.
15
20
16
21
After installed, you can use `aztec-up` to install specific versions.
echo -e "Foundry, Noir, and Barretenberg are bundled at the versions ${bold}${g}aztec${r} needs. Your own ${bold}${g}forge${r} / ${bold}${g}nargo${r} / ${bold}${g}bb${r} installs still work under their bare names."
0 commit comments