yarn compile:* prints Compiled <file> and exits 0 even when compact compile fails and writes no artifact. @openzeppelin/compact-builder 0.0.4 runs the compiler under script -qc, and script without -e returns 0 regardless of the child's status. A mock with a wrong import path passed CI-style compiles during the preset refactors and was only caught by counting artifacts.
Upstream fixed it in compact-tools #162, shipped as compact-builder 0.0.5. We never receive it: @openzeppelin/compact-cli ^0.0.3 pins builder ^0.0.4, which on a 0.0.x line excludes 0.0.5. compact-cli 0.1.1 pins builder ^0.0.5 and its deployer dependency is now published. Bump the cli to ^0.1.1 (Node 24, which the repo already targets), and pass --feature-zkir-v3 on the umbrella compile and build scripts, which the honest exit code shows have been failing silently for the ECDSA contracts.
yarn compile:*printsCompiled <file>and exits 0 even whencompact compilefails and writes no artifact.@openzeppelin/compact-builder0.0.4 runs the compiler underscript -qc, andscriptwithout-ereturns 0 regardless of the child's status. A mock with a wrong import path passed CI-style compiles during the preset refactors and was only caught by counting artifacts.Upstream fixed it in compact-tools #162, shipped as compact-builder 0.0.5. We never receive it:
@openzeppelin/compact-cli ^0.0.3pins builder^0.0.4, which on a 0.0.x line excludes 0.0.5. compact-cli 0.1.1 pins builder^0.0.5and its deployer dependency is now published. Bump the cli to^0.1.1(Node 24, which the repo already targets), and pass--feature-zkir-v3on the umbrellacompileandbuildscripts, which the honest exit code shows have been failing silently for the ECDSA contracts.