Update Aztec version to 4.3.0#261
Merged
Merged
Conversation
Bumps the pinned Aztec version from 4.2.0 to 4.3.0 across Nargo.toml, package.json, config, README, CLAUDE.md, and ONBOARDING docs. Also updates deployment call sites to match the 4.3.0 SDK API, which moves `contractAddressSalt` and `universalDeploy` from `send()` options into the `deploy()` deployment options.
The previous commit updated the package and config versions but left the CI workflow and devcontainer Dockerfile pinned at 4.2.0. That caused CI to install the 4.2.0 toolkit, codegen artifacts with the old DeployMethod pattern (constructor is protected in 4.3.0) and without the now-required `aztec_version` field, then run them against 4.3.0 JS packages — yielding TS build failures.
4.3.0 renames the bundled noir compiler binary to aztec-nargo (the installer note: "Your own forge / nargo / bb installs still work under their bare names"). The aztec CLI's `compile` command still spawns `nargo` internally, so a fresh 4.3.0 install with no user-provided nargo fails with `spawn nargo ENOENT`. Symlink aztec-nargo to nargo on PATH so `aztec compile` resolves it.
The 4.3.0 install layout exposes the noir compiler as ~/.aztec/current/bin/aztec-nargo, which is a symlink to the real binary at ~/.aztec/current/internal-bin/nargo. The bash `aztec` wrapper would normally prepend internal-bin before exec'ing the JS, but GitHub Actions PATH ordering puts node_modules/.bin/aztec ahead of the wrapper, so the wrapper is bypassed and internal-bin is never on PATH — and `aztec compile` fails with `spawn nargo ENOENT`. Add internal-bin to PATH directly.
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
1 participant
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
4.2.0to4.3.0acrossNargo.toml,package.json,config/local-network.json,README.md,CLAUDE.md, andONBOARDINGdocscontractAddressSaltanduniversalDeploymoved from.send()options into thedeploy()deployment options (scripts/multiple_wallet.ts,src/test/e2e/accounts.test.ts,src/utils/sponsored_fpc.ts)yarn.lockagainst the new versionsTest plan
yarn installsucceedsyarn compile && yarn codegensucceedsyarn test:nrpassesaztec start --local-network+yarn test:jspassesyarn deployworks against a fresh local network