Skip to content

Update Aztec to 5.0.0-rc.2#264

Merged
critesjosh merged 1 commit into
nextfrom
jc/update-next-v5-rc2
Jun 30, 2026
Merged

Update Aztec to 5.0.0-rc.2#264
critesjosh merged 1 commit into
nextfrom
jc/update-next-v5-rc2

Conversation

@critesjosh

Copy link
Copy Markdown
Collaborator

Summary

Bumps the next branch from Aztec 5.0.0-rc.1 to 5.0.0-rc.2, tracking the latest release. The testnet branch already moved to rc.2 in #263; this keeps next (local-network development) in sync.

Updates Nargo.toml, all @aztec/* packages, config/local-network.json, the CI/devcontainer toolchain version, README, and the onboarding docs.

rc.1 → rc.2 code changes

  • AztecAddress.fromStringAztecAddress.fromStringUnsafe (the fromString static was removed in rc.2).
  • Fee-juice claims now wait for the bridged L1→L2 message to be available before claiming — rc.2 needs more than two L2 blocks for the message to sync, so the old "deploy 2 contracts" approach raced. Affects src/test/e2e/accounts.test.ts and scripts/fees.ts.

Testing

Validated locally against a fresh 5.0.0-rc.2 local network:

  • yarn test:nr — 16/16 Noir TXE tests pass
  • yarn test:js — 16/16 e2e tests pass (incl. the fee-juice claim test)
  • tsc -p tsconfig.json --noEmit — clean
  • All local-network scripts pass: deploy-account, deploy, fees, multiple-wallet, profile, interaction-existing-contract

Track the latest release (the testnet moved to rc.2 in #263). Bump all
@Aztec packages, the aztec-nr dependency, the toolchain version
(CI + devcontainer), and docs from 5.0.0-rc.1 to 5.0.0-rc.2, plus the
two rc.1 -> rc.2 code fixes:

- AztecAddress.fromString -> AztecAddress.fromStringUnsafe.
- Fee-juice claims: wait for the bridged L1->L2 message to be available
  before claiming (rc.2 needs more than two blocks for the message to
  sync to L2).
@critesjosh critesjosh merged commit fb92588 into next Jun 30, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant