Update Aztec to v5.0.0-rc.1#262
Merged
Merged
Conversation
Bump all @aztec/* packages, the aztec-nr dependency, the toolchain version (Dockerfile/CI), and docs from 4.3.0 to 5.0.0-rc.1. Code changes for 5.0.0-rc.1 breaking changes: - Noir: MessageDelivery moved to `aztec::messages::delivery` and now uses constructor syntax (`MessageDelivery::onchain_constrained()`). - deploy_contract.ts: read the deployed instance from the send result (`DeployResultMined.instance`) and log the new PublicKeys hash fields (npkMHash / ivpkM / ovpkMHash / tpkMHash). - fees.ts: `GasSettings.fallback` now requires explicit `gasLimits`; derive them from the node's per-tx admission limit (`txsLimits.gas`). - accounts.test.ts: read the deployed contract from the send result rather than off the receipt.
ts-node's ESM loader does not resolve the `./*/lazy` subpath-pattern export of `@aztec/standard-contracts`, which `@aztec/pxe` now imports at runtime in 5.0.0-rc.1 (auth_registry / multi_call_entrypoint were demoted to standard contracts). It mis-resolves `auth-registry/lazy` to `auth-registry/lazy/index.js` and crashes every script. Switch the package.json script runner to tsx, which resolves package `exports` correctly. The Jest e2e tests already use their own resolver and are unaffected.
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
Updates the starter from 4.3.0 to 5.0.0-rc.1.
Version bumps
@aztec/*packages inpackage.json→5.0.0-rc.1Nargo.tomlaztec-nr dependency →tag = "v5.0.0-rc.1".devcontainer/Dockerfileand.github/workflows/local-network.yaml(AZTEC_VERSION) →5.0.0-rc.1README.md,ONBOARDING.md,docs/ONBOARDING.src.md,CLAUDE.md) andconfig/local-network.json→5.0.0-rc.1Code changes for 5.0.0-rc.1 breaking changes
src/main.nr):MessageDeliverymoved toaztec::messages::deliveryand now uses constructor syntax —MessageDelivery::onchain_constrained()instead ofMessageDelivery.ONCHAIN_CONSTRAINED.scripts/deploy_contract.ts: read the deployed instance from the send result (DeployResultMined.instance) instead of off the receipt, and log the newPublicKeyshash fields (npkMHash/ivpkM/ovpkMHash/tpkMHash).scripts/fees.ts:GasSettings.fallbacknow requires explicitgasLimits; derived from the node's per-tx admission limit (txsLimits.gas).src/test/e2e/accounts.test.ts: read the deployed contract from the send result rather than off the receipt.Testing
tsc --noEmit✅ cleanaztec compile+aztec codegen✅aztec test) ✅ 16/16yarn test:js, local network) ✅ 16/16 across 3 suitesOpening as a draft to let CI run.