Skip to content

feat: merge-train/spartan-v5 - #25156

Open
AztecBot wants to merge 1 commit into
v5-nextfrom
merge-train/spartan-v5
Open

feat: merge-train/spartan-v5#25156
AztecBot wants to merge 1 commit into
v5-nextfrom
merge-train/spartan-v5

Conversation

@AztecBot

@AztecBot AztecBot commented Aug 10, 2026

Copy link
Copy Markdown
Collaborator

BEGIN_COMMIT_OVERRIDE
fix: include standard-contracts historical artifacts in release image (#25155)
END_COMMIT_OVERRIDE

…#25155)

Since #25032, `@aztec/standard-contracts` has a top-level import of
historical artifact JSONs from
`standard-contracts/artifacts-historical/`. The release image
dockerignore ignores everything and then whitelists specific paths, and
it only whitelisted `standard-contracts/artifacts/` — so the historical
artifacts never made it into the image.

- Every node built from a v5-next release image crash-loops on startup
at ESM link time with `ERR_MODULE_NOT_FOUND` for
`HandshakeRegistry-5.0.1.json`.
- This has broken all spartan deploys from this line since 2026-07-29.
- The fix is a single whitelist entry:
`!/yarn-project/standard-contracts/artifacts-historical/`.

Split out from #25148 so the deploy fix can land independently of that
PR's review. Once this merges, #25148 will be rebased and its duplicate
commit will drop out.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants