v4.3.0
Overview
Migration difficulty: low. The only change likely to require operator action is the renaming of bundled binaries under an aztec- prefix.
Breaking changes
Bundled binaries renamed under aztec- prefix on PATH
aztec-up previously placed bundled tooling directly into $HOME/.aztec/current/bin under bare names (forge, cast, nargo, bb, pxe, txe, validator-client, blob-client, ...). Operators with their own forge or nargo install elsewhere on PATH could end up silently using the wrong binary depending on resolution order, and the bundle could shadow unrelated projects.
In v4.3.0, every bundled binary is exposed only under its aztec--prefixed name. Bare names are no longer placed on PATH by aztec-up.
Was on PATH | Now |
|---|---|
forge | aztec-forge |
cast | aztec-cast |
anvil | aztec-anvil |
chisel | aztec-chisel |
nargo | aztec-nargo |
noir-profiler | aztec-noir-profiler |
bb | aztec-bb |
bb-cli | aztec-bb-cli |
pxe | aztec-pxe |
txe | aztec-txe |
validator-client | aztec-validator-client |
blob-client | aztec-blob-client |
aztec, aztec-wallet, and aztec-up keep their existing names.
Operator action: any operator scripts, systemd units, dockerfiles, or run-books that invoke forge, cast, anvil, nargo, bb, pxe, txe, validator-client, or blob-client directly from the bundle path must switch to the aztec- prefixed names. References to aztec, aztec-wallet, and aztec-up are unaffected.
Other notable changes
These items do not require operator action but are called out in the v4.3.0 release notes:
- Sequencer signs the last block before archiver sync (#22117) — correctness and ordering improvement around block signing.
- Release image stamps
stdlib/package.jsonwith the release version (#23393) — fixes a published-artifact metadata mismatch that affected downstream consumers of the stdlib package. - macOS
aztec-upinstall ergonomics (#23310, #23335) —aztec-upnow falls back to no-timeout when/usr/bin/timeoutis absent, andadd_crate.shusesperl -iinstead of GNU-specificsed -i. Affects operators who bootstrap nodes viaaztec-upon macOS.
Troubleshooting
If a previously-working operator command suddenly errors with command not found: forge (or cast, nargo, bb, etc.) after upgrading to v4.3.0, switch the call site to the aztec- prefixed binary or install the standalone tool separately.