fix: include standard-contracts artifacts in release image#23753
Merged
Conversation
Thunkar
approved these changes
May 31, 2026
Collaborator
Author
Flakey Tests🤖 says: This CI run detected 1 tests that failed, but were tolerated due to a .test_patterns.yml entry. |
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
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.
Problem
V5 /
nextnet deployments crash on startup with:Root cause
release-image/Dockerfile.dockerignoreis an allowlist (*ignores everything, then!-includes specific paths). It explicitly re-includes theartifacts/directory forprotocol-contracts,noir-contracts.js,accounts,simulator, etc., and copies everydest/via!/yarn-project/*/dest/— but it has no entry forstandard-contracts/artifacts/.When auth-registry (and later public-checks / multi-call-entrypoint) was demoted into the new
standard-contractspackage (#23106), the allowlist was never updated. So the image shipsstandard-contracts/dest/but not its artifacts. At container startup the eager import indest/auth-registry/index.js(import '../../artifacts/AuthRegistry.json') resolves to a file that was excluded from the build context →ERR_MODULE_NOT_FOUND.This only affects the Docker release image. The npm tarball is unaffected because it uses
package.json'sfilesfield (which includesartifacts), a different mechanism — which is whynpm pack @aztec/standard-contractscontainsAuthRegistry.jsonwhile the deployed image does not.Fix
Add
standard-contracts/artifacts/to the dockerignore allowlist, matching the other contract-artifact packages. One line; same pattern as the existingprotocol-contracts/noir-contracts.jsentries.Verification
npm pack @aztec/standard-contracts@latestalready containsartifacts/AuthRegistry.json,PublicChecks.json(confirms source/files are correct; the gap is image-only).standard-contracts/artifacts/, so the JSON artifacts are copied to/usr/src/yarn-project/standard-contracts/artifacts/alongsidedest/, resolving the eager import.Created by claudebox · group:
slackbot