aia4-deploy-preflight

Deployment preflight checks are automated by executing the full build pipeline locally to catch and resolve issues like lockfile desync, image budget constraints, and missing files before they reach the deployment environment.

Common deployment preflight checks include detecting lockfile desync, validating image format and budget constraints, and verifying missing files. Running these checks locally prevents common failure classes from reaching the live deployment environment.

To run the automated preflight checks before a commit, execute 'npm run preflight' in your repository directory. This triggers the local deployment pipeline to identify and auto-remediate known issues.

Yes, auto-remediation automatically addresses known failure classes such as lockfile desync and image issues during local build pipeline execution, ensuring these problems are resolved before pushing code changes.

Yes, the deployment preflight process is designed to run locally and prevent issues from reaching the Coolify deployment environment. It requires local execution of the Coolify deploy pipeline to validate stability.

Running preflight checks before pushing ensures deployment stability by catching and fixing common failures locally. It also logs new failure classes and updates the preflight script to prevent future deployment issues.