laravel-verification

Topics in the source

• Laravel Verification Loop
• When to Use
• How It Works
• Phase 1: Environment Checks
• Phase 1.5: Composer and Autoload
• Phase 2: Linting and Static Analysis
• Phase 3: Tests and Coverage
• Phase 4: Security and Dependency Checks

Run before PRs, after major changes, and pre-deploy. Before opening a pull request for a Laravel project After major refactors or dependency upgrades Pre-deployment verification for staging or production Running full lint -> test -> security -> deploy readiness pipeline Run phases sequentially from environment checks through deployment readiness so each layer builds on the last. Environment and Composer checks gate everything else; stop immediately if they fail. Linting/static analysis should be clean before running full tests and coverage. Security and migration reviews happen after tests so you verify behavior before data or release steps. Build/deploy readiness and queue/scheduler checks are final gates; any failure blocks release. Verify .env is present and required keys exist Confirm APPDEBUG=false for production environments Confirm APPENV matches the target deployment (production, staging) If using Laravel Sail locally: If your project uses Psalm instead of PHPStan: Coverage (CI): CI example (format -> static analysis -> tests): Review destructive migrations carefully Ensure migration filenames follow YmdHis (e.g., 20250314154210createorderstable.php) and describe the change

This is an excerpt. Refer to the complete source and its current requirements.