Skip to content

chore: backport add aztecVersion to PXE schema_tests fixture (#22960) to v4-next#22962

Closed
AztecBot wants to merge 4 commits into
backport-to-v4-next-stagingfrom
claudebox/backport-22960-v4-next
Closed

chore: backport add aztecVersion to PXE schema_tests fixture (#22960) to v4-next#22962
AztecBot wants to merge 4 commits into
backport-to-v4-next-stagingfrom
claudebox/backport-22960-v4-next

Conversation

@AztecBot

@AztecBot AztecBot commented May 5, 2026

Copy link
Copy Markdown
Collaborator

Backport of #22960 (fix: add aztecVersion to PXE schema_tests fixture) to backport-to-v4-next-staging.

Dependency

This PR depends on #22958 (backport of #22872, which introduces the schema_tests fixture). #22960 only modifies a file added by #22872, so the cherry-pick has nothing to apply to without #22958.

This branch was based on claudebox/backport-22872-pxe-db-schema-test (PR #22958's branch), then rebased onto current backport-to-v4-next-staging HEAD (which now includes #22550feat: stamping aztec version into contract artifacts).

After #22958 merges, this PR should be rebased so the diff collapses to just the new fixture-version commit.

Why this fix is required for the v4-next backport story

PR #22550 (which added the required aztecVersion: string field on ContractArtifact) merged into backport-to-v4-next-staging AFTER #22958 was prepared. As a result, #22958 alone no longer builds against current staging — the buildSchemaContractArtifact() fixture is now missing a required field.

The #22960 fix supplies that missing field (aztecVersion: 'schema-fixture-version') and also updates the ContractStore.json snapshot accordingly. With both #22958 and this PR merged, the v4-next build is restored.

Cherry-pick

Clean cherry-pick of 7ce65770b7 (fix: add aztecVersion to PXE schema_tests fixture) on top of #22958's branch — only schema_tests.ts (1 line) and the ContractStore.json snapshot (2 hex blobs) changed.

Original PR: #22960

ClaudeBox log: https://claudebox.work/s/895b33635fc09211?run=1

ClaudeBox log: https://claudebox.work/s/895b33635fc09211?run=1

mverzilli and others added 4 commits May 5, 2026 17:36
Cherry-pick of 63dc224 onto backport-to-v4-next-staging. Conflicts in yarn-project/yarn.lock left as conflict markers; resolved in following commit.
v4-next still requires mkdirp@^1.0.3 (line 21033) while the new jest-file-snapshot dep introduced by #22872 brings mkdirp@^3.0.1. Kept both lockfile entries.
v4-next BlockHash class lacks the BlockHash.ZERO static introduced after the branch cut. Replaced with new BlockHash(Fr.ZERO) which is equivalent.
@AztecBot AztecBot added ci-draft Run CI on draft PRs. claudebox Owned by claudebox. it can push to this PR. labels May 5, 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
Addednpm/​jest-file-snapshot@​0.7.0971009576100

View full report

@benesjan

benesjan commented May 6, 2026

Copy link
Copy Markdown
Contributor

Realized this backport was unnecessary because the original PR got in before Martin's PXE DB backwards compatibility PR into backport-to-v4-next-staging and hence the fix will need to be in backport of Martin's PR here.

@benesjan benesjan closed this May 6, 2026
@benesjan benesjan deleted the claudebox/backport-22960-v4-next branch May 6, 2026 07:16
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.

3 participants