A build with 'critical errors' returns an 'OK' status code

Say I have a some modules containing issues. If I run cdf build on them, and the output is a message saying “Do not proceed to deploy” I would expect the resulting status code to be non-zero, so you can detect failures in deployment scripts.

Real example of the build unexpectedly returning a successful status-code:

I run this command: uv run cdf build -m modules/module1 -m modules/module2 -m modules/module3 && echo "This only prints if the previous command returns a Success status code"
 

This is a problem because CI/CD pipelines won’t catch that there are issues with the modules.​​​​​