Skip to content

fix(ci): restore noir 1.0.0-beta.21 yarn.lock entries on spartan-v5#23892

Closed
AztecBot wants to merge 1 commit into
merge-train/spartan-v5from
cb/fix-spartan-v5-noir-lockfile
Closed

fix(ci): restore noir 1.0.0-beta.21 yarn.lock entries on spartan-v5#23892
AztecBot wants to merge 1 commit into
merge-train/spartan-v5from
cb/fix-spartan-v5-noir-lockfile

Conversation

@AztecBot

@AztecBot AztecBot commented Jun 4, 2026

Copy link
Copy Markdown
Collaborator

Problem

CI on merge-train/spartan-v5 failed in the yarn-project build step (log 1780602818274491, commit 107b3361844). The yarn install --immutable step aborted with YN0028 frozen_lockfile_exception:

- "@aztec/noir-types": "npm:1.0.0-beta.22"
+ "@aztec/noir-types": "npm:1.0.0-beta.21"

Root cause

PR #23827 ("proofless tx lookup") is unrelated to Noir, but its commit on this branch inadvertently bumped the Noir package entries in yarn-project/yarn.lock from 1.0.0-beta.21 to 1.0.0-beta.22 (version, file: resolution hash 294c27893a3e, the noir_js checksum, and the noir_codegen/noir_js/noirc_abi dependency pins).

The noir/noir-repo submodule pointer on this branch was not changed — it stays at f1a4575 whose packages declare 1.0.0-beta.21. So the committed lockfile (beta.22) no longer matched what the portal/file: resolution produces from the submodule (beta.21), and --immutable correctly refused. This is the exact drift the recently-added "fail loudly on yarn.lock drift" check (#23882) is meant to catch.

The beta.22 entries are residue of a reverted Noir bump — commit 9e53e1f ("revert two bad automerges") had already restored the submodule to the beta.21 pointer f1a4575 with the matching beta.21 lockfile.

Fix

Revert only the Noir lockfile entries back to 1.0.0-beta.21. The resulting yarn-project/yarn.lock is byte-identical to commit 9e53e1f — the canonical consistent state that pairs submodule f1a4575 with the beta.21 lockfile (file: checksum ef758950…, resolution hash 294c27). No other lockfile changes; the submodule pointer is untouched.

Verification

With noir/packages materialized from the build cache (real beta.21 content), the previously-failing step now passes:

yarn install --immutable  →  exit 0 (no YN0028; only benign peer-dep warnings)

Only yarn-project/yarn.lock changes; noir/noir-repo is unmodified.


Created by claudebox · group: slackbot

@AztecBot AztecBot added ci-draft Run CI on draft PRs. ci-no-squash claudebox Owned by claudebox. it can push to this PR. private-port-next labels Jun 4, 2026
@socket-security

Copy link
Copy Markdown

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

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatednpm/​@​aztec/​noir-noir_js@​1.0.0-beta.22 ⏵ 1.0.0-beta.21100100100100100

View full report

@AztecBot

AztecBot commented Jun 4, 2026

Copy link
Copy Markdown
Collaborator Author

Flakey Tests

🤖 says: This CI run detected 1 tests that failed, but were tolerated due to a .test_patterns.yml entry.

\033FLAKED\033 (8;;http://ci.aztec-labs.com/ef894e637b24731f�ef894e637b24731f8;;�):  yarn-project/end-to-end/scripts/run_test.sh simple src/e2e_epochs/epochs_invalidate_block.parallel.test.ts "proposer invalidates multiple checkpoints" (554s) (code: 0) group:e2e-p2p-epoch-flakes

@AztecBot

Copy link
Copy Markdown
Collaborator Author

Automatically closing this stale claudebox draft PR (no updates for 5+ days). Re-open if still needed.

@AztecBot AztecBot closed this Jun 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci-draft Run CI on draft PRs. ci-no-squash claudebox Owned by claudebox. it can push to this PR. private-port-next

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant