chore: upgrade v4.3.0

[0xLeopoldo]

No description provided.

[qodo-code-review]

Review Summary by Qodo

Upgrade Aztec boilerplate to v4.3.0-rc.1

✨ Enhancement

Walkthroughs

Description

• Upgrade Aztec dependencies from 4.2.0 to 4.3.0-rc.1
• Update Noir contract dependency tag to v4.3.0-rc.1
• Add @aztec/foundation resolution to package.json
• Update pre-commit hook to use aztec-nargo command

Diagram

flowchart LR
  A["Current Version 4.2.0"] -- "Upgrade dependencies" --> B["Version 4.3.0-rc.1"]
  B -- "Update Noir tag" --> C["Nargo.toml v4.3.0-rc.1"]
  B -- "Add foundation resolution" --> D["package.json resolutions"]
  B -- "Update pre-commit" --> E["aztec-nargo command"]

Loading

File Changes

1. package.json Dependencies +11/-10

Update all Aztec dependencies to 4.3.0-rc.1

• Bump project version from 4.2.0 to 4.3.0-rc.1
• Update all @aztec/* dependencies to 4.3.0-rc.1
• Update aztecVersion config to 4.3.0-rc.1
• Add @aztec/foundation 4.3.0-rc.1 to resolutions

package.json

---

2. src/nr/counter_contract/Nargo.toml Dependencies +1/-1

Update Noir aztec dependency tag

• Update aztec dependency tag from v4.2.0 to v4.3.0-rc.1

src/nr/counter_contract/Nargo.toml

---

3. .husky/pre-commit ⚙️ Configuration changes +1/-1

Update pre-commit hook command

• Replace nargo with aztec-nargo command in pre-commit hook

.husky/pre-commit

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (2) 📘 Rule violations (0) 📎 Requirement gaps (0)

1. Undeclared aztec-nargo hook 🐞 Bug ☼ Reliability

Description

The pre-commit hook now executes aztec-nargo fmt, but aztec-nargo is not declared in
package.json, so a clean checkout with only yarn install cannot guarantee the command exists and
commits will fail. This is a new workflow dependency introduced by the PR.

Code

.husky/pre-commit[1]

Evidence

The hook now invokes aztec-nargo but the repo’s JS dependencies/scripts don’t include an
aztec-nargo package/binary, and the README setup steps don’t mention installing it; Husky is
enabled via the prepare script so this hook will execute on commit.

.husky/pre-commit[1-2]
package.json[8-19]
package.json[23-33]
README.md[30-34]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`.husky/pre-commit` calls `aztec-nargo fmt` directly, but the repo does not declare/provide an `aztec-nargo` binary via `package.json`. This can break `git commit` on machines where `aztec-nargo` isn’t already installed on PATH.

## Issue Context
Husky is enabled via `prepare: husky`, so contributors will hit this hook during commits.

## Fix Focus Areas
- .husky/pre-commit[1-2]
- package.json[8-19]
- package.json[23-33]
- README.md[30-34]

## What to change
Pick one approach and make it deterministic after `yarn install`:
1. **Prefer:** add a package-provided command and run it via yarn (e.g., `"format:nr": "aztec-nargo fmt"` then in the hook `yarn -s format:nr`) *and* add the dependency that provides `aztec-nargo` (if it exists as an npm package/binary).
2. If `aztec-nargo` is intentionally external (installed with the Aztec toolchain), **document it explicitly** in README Setup and consider guarding the hook with a clear error message when the binary is missing.
3. Alternatively, if supported, invoke formatting through an existing tool that the project already requires (e.g., an `aztec ...` subcommand) rather than a separate binary.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

2. Benchmark stack out-of-sync 🐞 Bug ≡ Correctness

Description

The repo upgrades @aztec/* to 4.3.0-rc.1 but keeps @defi-wonderland/aztec-benchmark on a 4.2.0
prerelease, so yarn benchmark/CI benchmark workflows will run with a different Aztec JS/wallet
stack than the project dependencies. yarn.lock shows aztec-benchmark depends on @aztec/aztec.js and
@aztec/wallets 4.2.0 while 4.3.0-rc.1 is also present, creating a mixed-version runtime.

Code

package.json[R24-31]

Evidence

The repo now depends on Aztec 4.3.0-rc.1, but the benchmark package and benchmark CI workflows are
still pinned to a 4.2.0 prerelease; yarn.lock also shows the benchmark package pulls
@aztec/aztec.js/@aztec/wallets 4.2.0 while 4.3.0-rc.1 is present, proving a mixed-version benchmark
runtime.

package.json[23-33]
yarn.lock[1405-1414]
yarn.lock[420-452]
.github/workflows/pr-checks.yml[15-16]
.github/workflows/update-baseline.yml[16-19]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`@defi-wonderland/aztec-benchmark` and the reusable benchmark workflows are pinned to a 4.2.0 prerelease while the repo’s `@aztec/*` dependencies are now 4.3.0-rc.1. This makes benchmark runs and benchmark CI operate with an older Aztec stack than the codebase.

## Issue Context
- `package.json` pins `@defi-wonderland/aztec-benchmark` to a `4.2.0-prerelease.*` tarball.
- The same prerelease ref is used in `.github/workflows/*` for benchmark workflows.
- `yarn.lock` shows aztec-benchmark depends on `@aztec/aztec.js@4.2.0`/`@aztec/wallets@4.2.0` while the repo uses `4.3.0-rc.1`, resulting in mixed versions.

## Fix Focus Areas
- package.json[23-33]
- yarn.lock[420-452]
- yarn.lock[1405-1414]
- .github/workflows/pr-checks.yml[15-16]
- .github/workflows/update-baseline.yml[16-19]

## What to change
1. Bump `@defi-wonderland/aztec-benchmark` to a release/prerelease that is built for Aztec `4.3.0-rc.1` (or whatever benchmark release matches this Aztec RC).
2. Update the referenced benchmark reusable workflows (`pr-benchmark.yml` / `update-baseline.yml`) to the corresponding benchmark workflow ref.
3. Regenerate `yarn.lock` so benchmark and Aztec libraries resolve consistently for the intended stack.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

• Author self-review: I have reviewed the code review findings, and addressed the relevant ones.

[cubic-dev-ai]

No issues found across 4 files

_{Re-trigger cubic}

[qodo-code-review]

1. Undeclared aztec-nargo hook 🐞 Bug ☼ Reliability

The pre-commit hook now executes aztec-nargo fmt, but aztec-nargo is not declared in
package.json, so a clean checkout with only yarn install cannot guarantee the command exists and
commits will fail. This is a new workflow dependency introduced by the PR.

Agent Prompt

## Issue description
`.husky/pre-commit` calls `aztec-nargo fmt` directly, but the repo does not declare/provide an `aztec-nargo` binary via `package.json`. This can break `git commit` on machines where `aztec-nargo` isn’t already installed on PATH.

## Issue Context
Husky is enabled via `prepare: husky`, so contributors will hit this hook during commits.

## Fix Focus Areas
- .husky/pre-commit[1-2]
- package.json[8-19]
- package.json[23-33]
- README.md[30-34]

## What to change
Pick one approach and make it deterministic after `yarn install`:
1. **Prefer:** add a package-provided command and run it via yarn (e.g., `"format:nr": "aztec-nargo fmt"` then in the hook `yarn -s format:nr`) *and* add the dependency that provides `aztec-nargo` (if it exists as an npm package/binary).
2. If `aztec-nargo` is intentionally external (installed with the Aztec toolchain), **document it explicitly** in README Setup and consider guarding the hook with a clear error message when the binary is missing.
3. Alternatively, if supported, invoke formatting through an existing tool that the project already requires (e.g., an `aztec ...` subcommand) rather than a separate binary.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

[0xLeopoldo]

False positive — aztec-nargo ships with the Aztec CLI toolchain (already listed as a prerequisite in the README, same as aztec compile/codegen/test used in our scripts) and isn't published to npm, so it can't be declared as a package dependency.

[qodo-code-review]

Persistent review updated to latest commit 9c7152a

[cubic-dev-ai]

0 issues found across 3 files (changes from recent commits).

_{Re-trigger cubic}

[github-actions]

Benchmark Comparison

CPU	Cores	RAM	Arch
AMD EPYC 7763 64-Core Processor	16	63 GiB	x64

Contract: counter

🚦	Function	Gates			DA Gas			L2 Gas			Proving Time (ms)
		Base	PR	Diff	Base	PR	Diff	Base	PR	Diff	Base	PR	Diff
🟢	increment	449,058	416,973	-32,085 (-7.1%)	192	192		627,249	627,207	-42 (-0.0%)	N/A	N/A

[wei3erHase]

👍