Skip to content

fix(ci): restore yarn.lock to noir beta.21 on merge-train/spartan-v5#23891

Closed
AztecBot wants to merge 1 commit into
merge-train/spartan-v5from
cb/spartan-v5-yarnlock-beta21
Closed

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

Conversation

@AztecBot

@AztecBot AztecBot commented Jun 4, 2026

Copy link
Copy Markdown
Collaborator

Problem

CI on merge-train/spartan-v5 is failing in the [yarn-project] step (log). The yarn install --immutable substep aborts with YN0028 (lockfile would be modified):

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

Root cause

The noir submodule and yarn.lock drifted out of sync on the branch:

  1. 9e53e1f805e ("revert two bad automerges") moved the noir/noir-repo submodule back to f1a4575 (v1.0.0-beta.21) and, at that commit, yarn.lock correctly referenced the @aztec/noir-* packages at beta.21.
  2. The next commit, 107b3361844 (feat!: proofless tx lookup in getTxByHash and getTxsByHash #23827, proofless tx lookup), carried a stale yarn.lock that re-pinned the six @aztec/noir-* entries at npm:1.0.0-beta.22 (yarn.lock is a binary-detected file, so this regression was silent in the diff).

Result: noir packages build at beta.21 but the lockfile demands beta.22, so yarn install --immutable wants to rewrite it → CI fails.

Fix

Restore yarn-project/yarn.lock to the beta.21 state from 9e53e1f805e. The diff is exactly the six @aztec/noir-* entries (versions, the noir_js resolution hash 893a3e294c27, and its checksum) — nothing else. This is precisely the lockfile yarn regenerates against the built beta.21 noir packages.

Verification

  • Built the beta.21 noir JS packages (noir/bootstrap.sh build_packages, cache hit) and confirmed noir/packages/* declare 1.0.0-beta.21.
  • cd yarn-project && yarn install --immutable now exits 0 — this is the exact substep that failed in the CI log — and leaves the lockfile unchanged.

Full ./bootstrap.sh ci-full-no-test-cache could not run to completion in the sandbox (no docker / remote build cache, so the native barretenberg C++ and cross-compile targets build from scratch and time out before reaching [yarn-project]). The CI failure was exclusively the immutable-install drift in [yarn-project], which is deterministically resolved here.

The 'revert two bad automerges' commit (9e53e1f) moved the noir
submodule back to v1.0.0-beta.21, but the subsequently-merged proofless
tx lookup PR (#23827) carried a stale yarn.lock pinning the @aztec/noir-*
packages at npm:1.0.0-beta.22. This drift made 'yarn install --immutable'
fail in the yarn-project CI step.

Restore the six @aztec/noir-* entries (versions, resolution hash, and
checksum) to the beta.21 values that match the noir submodule on this
branch. This is exactly the lockfile yarn regenerates against the built
beta.21 noir packages, so 'yarn install --immutable' now passes.
@AztecBot AztecBot added ci-draft Run CI on draft PRs. claudebox Owned by claudebox. it can push to this PR. 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

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. claudebox Owned by claudebox. it can push to this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant