[AztecBot]

Nightly bump 6.1.0-nightly.20261025 → 6.1.0-nightly.20261102.

Healthcheck / nightly tag run: aztec-packages run 41386581029 (head 3614971ee0).

Changes

Generated by node scripts/update.js:

• @aztec-labs/* pins in every workspace package.json + yarn.lock
• .aztecrc
• aztec-nr / aztec-node tags in the 4 contract Nargo.toml files

@aztec-foundation/* resolves to 6.0.0-rc.7. No migration fixes were needed. yarn format:fix produced no changes.

Local verification

All on Node 26.12.1, each run once:

• yarn build: 7/7 tasks passed
• yarn test: 11/11 tasks passed. swap 4/4, embedded-wallet 11/11, contracts-aztec 29/29, e2e playwright 10/10 against aztec start --local-network

Notes

• Series: the nightly dispatch describes this as the v5 nightly, but update.js follows the current pin, so next tracks v6 (6.1.0-nightly).
• Same upstream head as yesterday: this tag run and the run behind #208 both report head 3614971ee0. I did not compare the published packages between the two nightlies.
• Supersedes chore(nightly): bump @aztec-labs/* to 6.1.0-nightly.20261101 #208 if merged first: chore(nightly): bump @aztec-labs/* to 6.1.0-nightly.20261101 #208 (6.1.0-nightly.20261101) is still open, and it edits the same pins. It has not been closed here.
• Publish timing: npm published aztec.js at about 04:10 UTC, but @aztec-labs/noir-protocol-circuits-types only appeared at about 04:24 UTC. update.js and yarn install fail until the whole set is up, and checking only the nightly dist-tag does not show that.
• Bump host setup (nothing committed):
  • The CLI installer needs Node ≥ 26.12.0 and the host had 24.15.0, so Node 26.12.1 was put on PATH.
  • On Node 26, node-gyp could not download the Node headers while building bcrypto (InvalidArgumentError: invalid onError method from EnvHttpProxyAgent). Setting npm_config_nodedir to the local Node install avoided the download.
• Warnings seen, neither failing the build or tests:
  • The contract compile warns that amm_contract and proof_of_password tests should live in a dedicated test crate.
  • The e2e Vite server logs Big integer literals are not available in the configured target environment.
  • I did not check whether these are new in this nightly.

---

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

[github-actions]

🚀 Deployed to Vercel!

Bridge: https://aztec-kit-bridge-next-1nst9zsk3-thunkars-projects.vercel.app
FPC Operator: https://aztec-kit-fpc-next-c4m40x5ks-thunkars-projects.vercel.app
Swap: https://aztec-kit-swap-next-1c3nyqikq-thunkars-projects.vercel.app