smithery.ai

noir-sync-update

Bump the Noir compiler version in aztec-packages and perform every follow-on update.

First seen Mar 30, 2026

Installation

$ npx skills add https://smithery.ai

Summary

  • Bump the Noir compiler version in aztec-packages and perform every follow-on update.
  • Use whenever the noir/noir-repo submodule changes or on a request to "bump/update the noir compiler version to X" or "bump the noir submodule".
  • Covers the submodule pointer, avm-transpiler Cargo.lock, yarn-project yarn.lock, and noir-projects formatting.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,712 B
  • docs SUMMARY.md 107 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Noir Sync Update

To bump the Noir compiler (a request like "bump the noir compiler version to X", "update noir to <ref>") or to reconcile the tree after any manual noir/noir-repo submodule change, run the single source-of-truth script:

noir/scripts/bump_noir_compiler.sh <ref>

<ref> is any noir-lang/noir git reference — a release tag (v1.0.0-beta.23), a nightly tag (nightly-2026-06-02), a branch, or a commit. With no <ref> it uses the latest nightly-* tag. The script bumps the submodule, refreshes avm-transpiler/Cargo.lock and yarn-project/yarn.lock, reformats noir-projects, and stages everything. It does not commit.

Read the script's header and inline comments for what each step does, why, and how to recover when a step fails (e.g. a changed transitive Cargo dependency, or the format step needing a built nargo). After it runs:

  1. Verify each artifact actually changed with git status from the repository root

(running git status from inside a subdirectory can silently report nothing).

  1. Review the staged diff and commit, e.g. git commit -m "chore: update Noir to <ref>".

Requires a real toolchain (cargo, corepack/yarn, a built nargo); the steps are best-effort in a bare checkout. If a step warns, follow the guidance it prints and re-run before committing.