code-change-verification

Verify code changes in a monorepo by running a mandatory verification stack that installs dependencies, builds the project, lints, type-checks generated declarations, and runs tests in parallel. This enforces a production-grade workflow with fail-fast reporting to ensure changes are safe to merge.

Running lint and tests in parallel during continuous integration is handled by executing independent checks concurrently and stopping on the first failure. This fail-fast approach provides clear reporting and guidance for remediation, ensuring rapid feedback without waiting for the entire sequence to finish.

This code verification workflow supports macOS, Linux, and Windows environments. It provides platform-agnostic guidance using shell scripts and a PowerShell wrapper, ensuring consistent verification results across different operating systems.

You need to run a full build and type check for generated declarations when changes impact runtime code, tests, or build configuration. This ensures that all generated type definitions are valid and that the project maintains type safety before being marked complete.

A monorepo build check fails before running tests because the verification sequence enforces a fail-fast policy, stopping execution immediately when a build error is detected. This prevents subsequent steps like linting and testing from running on a broken build, providing clear reporting for remediation.

Yes, you can use this verification sequence for changes that modify build configuration. It is explicitly designed to apply to changes impacting runtime code, tests, or build and test configuration within a monorepo, ensuring configuration updates do not break the dependency installation or build process.