chore: bump toolchain pins to 6.0.0-nightly.20261001

[fcarreiro]

Bumps the labs toolchain from 6.0.0-rc.2 to 6.0.0-nightly.20261001, the AztecProtocol/aztec-packages v6 nightly cut at cf7ea33e26 (after AztecProtocol/aztec-packages#25565).

• BB_VERSION: 6.0.0-rc.2 → 6.0.0-nightly.20261001
• NOIR_VERSION: unchanged at 1.0.0-rc.3; the nightly's noir/noir-repo submodule is 5a7ee9bf5e, tagged v1.0.0-rc.3

Since 6.0.0-rc.2, v6 gains the labs bump to this repo's main (AztecProtocol/aztec-packages#25560) and AztecProtocol/aztec-packages#25548 (bb.js reports a dead bb process as retryable and replaces it on request).

The rewrite is ./labs-aztec-toolchain/bootstrap.sh set-pins 6.0.0-nightly.20261001 1.0.0-rc.3 (bootstrap.sh, aztec-nr's Nargo.toml, the docs examples, docs/package.json and the 23 @aztec-foundation/* resolutions in yarn-project/package.json), plus yarn in yarn-project and docs. The lockfile diffs are the 24 @aztec-foundation/* entries moving to the nightly and nothing else.

Verification

• every @aztec-foundation/* resolution and the bb/bb-avm per-platform tarballs exist on npm at 6.0.0-nightly.20261001
• node labs-aztec-toolchain/pins.mjs check: no drift
• ./labs-aztec-toolchain/bootstrap.sh: provisions bb and bb-avm 6.0.0-nightly.20261001
• ./bootstrap.sh in noir-projects/, then in yarn-project/: pass; the standard contracts build from the existing pinned tarball, and no tracked file changes

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​aztec-foundation/​noir-types@​6.0.0-rc.2 ⏵ 6.0.0-nightly.20261001	+1			+1
	npm/​@​aztec-foundation/​noir-noir_js@​6.0.0-rc.2 ⏵ 6.0.0-nightly.20261001				+1
	npm/​@​aztec-foundation/​l1-artifacts@​6.0.0-rc.2 ⏵ 6.0.0-nightly.20261001	+1			+1
	npm/​@​aztec-foundation/​noir-noir_codegen@​6.0.0-rc.2 ⏵ 6.0.0-nightly.20261001	+1			+1
	npm/​@​aztec-foundation/​noir-noirc_abi@​6.0.0-rc.2 ⏵ 6.0.0-nightly.20261001	+1			+1
	npm/​@​aztec-foundation/​ipc-runtime@​6.0.0-rc.2 ⏵ 6.0.0-nightly.20261001	+1			+1
	npm/​@​aztec-foundation/​mock-protocol-circuits-artifacts@​6.0.0-rc.2 ⏵ 6.0.0-nightly.20261001			+1	+1
	npm/​@​aztec-foundation/​protocol-contracts-artifacts@​6.0.0-rc.2 ⏵ 6.0.0-nightly.20261001	-5		+1	+1
	npm/​@​aztec-foundation/​noir-acvm_js@​6.0.0-rc.2 ⏵ 6.0.0-nightly.20261001	+1			+1
	npm/​@​aztec-foundation/​cdb@​6.0.0-rc.2 ⏵ 6.0.0-nightly.20261001	+1			+1
	npm/​@​aztec-foundation/​bb-avm-sim@​6.0.0-rc.2 ⏵ 6.0.0-nightly.20261001	+1			+1
	npm/​@​aztec-foundation/​protocol-circuits-artifacts@​6.0.0-rc.2 ⏵ 6.0.0-nightly.20261001	-2		+1	+1
	npm/​@​aztec-foundation/​constants-codegen@​6.0.0-rc.2 ⏵ 6.0.0-nightly.20261001	+1			+1
	npm/​@​aztec-foundation/​wsdb@​6.0.0-rc.2 ⏵ 6.0.0-nightly.20261001	+1			+1
	npm/​@​aztec-foundation/​bb.js@​6.0.0-rc.2 ⏵ 6.0.0-nightly.20261001	+1		+1	+1

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Priority	Alert  (click "▶" to expand/collapse)	Action
	Obfuscated code: npm @aztec-foundation/protocol-circuits-artifacts is 78.0% likely obfuscated Confidence: 0.78 Location: Package overview From: yarn-project/noir-protocol-circuits-types/package.json → npm/@aztec-foundation/protocol-circuits-artifacts@6.0.0-nightly.20261001 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aztec-foundation/protocol-circuits-artifacts@6.0.0-nightly.20261001. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Block
	Obfuscated code: npm @aztec-foundation/protocol-circuits-artifacts is 95.0% likely obfuscated Confidence: 0.95 Location: Package overview From: yarn-project/noir-protocol-circuits-types/package.json → npm/@aztec-foundation/protocol-circuits-artifacts@6.0.0-nightly.20261001 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aztec-foundation/protocol-circuits-artifacts@6.0.0-nightly.20261001. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Block
	Obfuscated code: npm @aztec-foundation/protocol-circuits-artifacts is 98.0% likely obfuscated Confidence: 0.98 Location: Package overview From: yarn-project/noir-protocol-circuits-types/package.json → npm/@aztec-foundation/protocol-circuits-artifacts@6.0.0-nightly.20261001 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aztec-foundation/protocol-circuits-artifacts@6.0.0-nightly.20261001. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Block
	Obfuscated code: npm @aztec-foundation/protocol-contracts-artifacts is 96.0% likely obfuscated Confidence: 0.96 Location: Package overview From: yarn-project/aztec.js/package.json → npm/@aztec-foundation/protocol-contracts-artifacts@6.0.0-nightly.20261001 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@aztec-foundation/protocol-contracts-artifacts@6.0.0-nightly.20261001. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Block

View full report

[greptile-apps]

Confidence Score: 5/5

[High risk] Bumps toolchain and build dependencies to nightly version.

The PR appears safe to merge based on the reviewed changes.

Summary

The PR moves the Barretenberg toolchain and associated Aztec package pins from 6.0.0-rc.2 to 6.0.0-nightly.20261001 while retaining Noir 1.0.0-rc.3.

• Updates Noir Git dependencies, documentation examples, npm resolutions, and both Yarn lockfiles to the corresponding nightly pins.
• No actionable issue was established from the changed files.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    BB["BB_VERSION: 6.0.0-nightly.20261001"]
    BB --> Nargo["Aztec package Git dependencies"]
    BB --> Yarn["yarn-project resolutions and lockfile"]
    BB --> Docs["Docs package, examples, and lockfile"]
    BB --> Binaries["Provisioned bb and bb-avm"]
    Noir["NOIR_VERSION: 1.0.0-rc.3"] --> NargoCompiler["Provisioned nargo"]

Loading

_{Reviews (1) · Last reviewed commit: "chore: bump toolchain pins to 6.0.0-nigh..."}

[fcarreiro]

(Written by Claude on behalf of Facundo)

@SocketSecurity ignore npm/@aztec-foundation/protocol-circuits-artifacts@6.0.0-nightly.20261001