chore(nightly): bump @aztec/* to 5.3.0-nightly.20260922

[AztecBot]

Nightly bump of the @aztec/* toolchain and contract tags.

• Version: 5.3.0-nightly.20260827 → 5.3.0-nightly.20260922
• Healthcheck run: https://github.com/AztecProtocol/aztec-packages/actions/runs/35685804643 (Nightly Release Tag, next @ f953bd3)

Produced by SHELL=/bin/bash CI=1 node scripts/update.js: 7 workspace package.json files, .aztecrc, 4 Nargo.toml files, and yarn.lock.

Verification

All run locally against the bumped pin:

Check	Result
yarn format:fix	no drift
yarn build	7/7 tasks, incl. Noir compile + codegen
yarn test	11/11 tasks, 10/10 playwright e2e passed (8.0m)

No migration fixes were needed — this is a pure version bump despite spanning ~26 days of nightlies.

Release-infra problem this bump hit

The npm packages and the v5.3.0-nightly.20260922 git tags (aztec-packages, aztec-nr) all published normally, but the CLI toolchain installer assets for this version were never uploaded. Both https://install.aztec-labs.com/5.3.0-nightly.20260922/install and .../versions return 404, so aztec-up / the VERSION= root installer cannot install the pinned toolchain at all. This is not publish lag — it was still 404 after 20 minutes of polling, and the gap is wide:

Version	Installer asset
5.3.0-nightly.20260827	200
5.3.0-nightly.20260901	200
5.3.0-nightly.20260905 … 20260919	404
5.3.0-nightly.20260920	200
5.3.0-nightly.20260921	404
5.3.0-nightly.20260922	404

That sparse window lines up with this repo's pin having been stuck on 20260827 for nearly a month.

To verify this bump anyway, the toolchain was reconstructed rather than installed:

• nargo: taken from the 20260920 bundle. The noir/noir-repo submodule is the same commit (75061fab15986eedee4e7d9104ff87dd9fa4ca10) at both the 20260920 and 20260922 tags, and the installed nargo 1.0.0-beta.25 reports exactly that hash — so it is bit-identical to what 20260922's bundle would have shipped.
• foundry: 1.4.1, which is the pin in bootstrap.sh at the 20260922 tag and matches the 20260920 manifest.
• aztec CLI + bb.js: installed from npm at exactly 5.3.0-nightly.20260922.

So the verification above ran against the correct compiler and the correct CLI; only the delivery mechanism was substituted.

Follow-up worth filing separately

scripts/update.js masks this failure. Its CI path runs:

exec(`curl -fsSL "https://install.aztec.network/${version}/install" | VERSION="${version}" bash`);

A pipeline's exit status is that of its last command, so the curl 404 is discarded, bash succeeds on empty input, and the script prints ✓ Aztec CLI installed (CI mode) having installed nothing. The failure only surfaces two steps later as command not found: aztec during contract compilation. Checking curl separately (or set -o pipefail) would report the missing installer asset directly.

---

Created by claudebox · group: aztec-kit-nightly · Slack thread