chore(backport-to-v4): fix: released contract artifact aztec version (#23470)#23851
Merged
Conversation
alexghr
approved these changes
Jun 4, 2026
1 task
aminsammara
added a commit
that referenced
this pull request
Jun 4, 2026
## Summary Adds the third bug fix that landed on `v4` (via backport PR #23851 of #23470) to the existing `## [4.3.1]` `CHANGELOG.md` entry so the section reflects what v4.3.1 actually ships. Single-line change in `CHANGELOG.md` only — no version-file or manifest changes. Manifest stays at 4.3.1. ## What v4.3.1 contains after this lands - `prover: wait for previous epoch to be proven` (#23457) - `stdlib: guard tip-store finalize against deleting live tips` (backport of #23295, via #23505) - `release-image: re-stamp aztec_version into released noir-contracts artifacts` (backport of #23470, via #23851) — **new entry, fixes the v4.3.1 ci-compat-e2e failure** ## After merging Force-move the `v4.3.1` tag to the merge commit of this PR (safe — nothing has been published as 4.3.1 yet: npm has only 4.3.0, Docker Hub returns 404 for `aztec:4.3.1`, GitHub Release for v4.3.1 doesn't exist). ## Test plan - [ ] Visual check that the `## [4.3.1]` section in `CHANGELOG.md` lists all three fixes
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
3 participants
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.
Summary
Backport of #23470 (by @benesjan) from
v4-nexttov4.This is needed to unblock the v4.3.1 release. The v4.3.0 release shipped contract artifact JSONs with
aztec_version: "dev"baked in (becauseREF_NAMEwasn't correctly populated during release-image build), which causesci-compat-e2eon v4 to fail withArtifact version mismatch: expected 4.3.0 but got dev. The same failure was blocking v4.3.1 publish.The fix re-stamps the version into the artifact later in the release process where the actual version is reliably available.
Cherry-pick details
v4-next:a2d104a1b4(merge commit of fix: released contract artifact aztec version #23470)-m 1(parent 1 = v4-next mainline) — applied cleanly with no conflicts.ci3/release_prep_package_json(+10)noir-projects/noir-contracts/bootstrap.sh(+11 / -10)release-image/Dockerfile(+12)yarn-project/end-to-end/src/fixtures/setup.ts(+9)After merging
v4.3.1CHANGELOG entry on v4 to include this fix.v4.3.1git tag to the new v4 HEAD (safe — nothing has been published as 4.3.1 yet: npm has only 4.3.0, Docker Hub returns 404 foraztec:4.3.1, GitHub Release for v4.3.1 doesn't exist).ci-release-publishshould run for real.Test plan
ci-compat-e2e)"dev"