chore: single script to bump the Noir compiler version#24726
Draft
AztecBot wants to merge 4 commits into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Makes bumping the Noir compiler a single, discoverable, complete operation. One script does everything; the skill and docs just point at it.
Bumping Noir must move several tracked artifacts together, or the tree is inconsistent and CI fails:
noir/noir-reposubmodule pointeravm-transpiler/Cargo.lock(the transpiler depends on noir crates by path)yarn-project/yarn.lock(picks up noir JS package version /file:hash changes)noir-projectsformatting (a compiler bump can change formatter output)Changes
noir/scripts/bump_noir_compiler.sh(new) — the single source of truth. Fetches<ref>into the shallow submodule and checks it out, refreshesCargo.lockvia targetedcargo update -p <noir crates only>(honouring the repo's lockfile-discipline rule), refreshesyarn.lockviayarn install --mode=update-lockfile, reformatsnoir-projects, and stages all of it.<ref>is a noir-lang/noir ref — release tagv1.0.0-beta.23, nightlynightly-2026-06-02, branch, or commit; no arg → latestnightly-*tag. Stages but does not commit. All the operational knowledge (why targeted cargo update, the expected-version sanity check against.release-please-manifest.json, "don't edit noir/noir-repo to fix the transpiler build", the format-needs-nargo note, git-status-from-root) lives as inline comments on the relevant sections..claude/skills/noir-sync-update— rewrote thedescriptionso a "bump the noir compiler version to X" request actually surfaces this skill (the old wording didn't match), and reduced the body to a pointer at the script rather than a parallel set of manual steps. One source of truth, not two.CLAUDE.md—<bumping_noir>block points straight at the script (surfaced via the skill)..github/workflows/pull-noir.yml— nightly auto-bump PR delegates its submodule + lockfile step to the script. No functional change to its PR-creation behavior.Notes
The update/format steps need a real toolchain (cargo, corepack/yarn, a built nargo); in a bare checkout each step warns rather than aborting, so a partial run still leaves a useful diff to finish by hand.