Release Smoke Check

Run a standardized smoke-check sequence to execute lint, typecheck, tests, and build on your release branch. This captures exit codes and the first actionable error to guide debugging and reporting.

A smoke check sequence is a lightweight, repeatable validation process that runs lint, typecheck, tests, and build to detect regressions before shipping, providing a concise pass/fail summary to accelerate release decisions.

Yes, you can run the smoke check sequence locally when CI failures require reproduction. It applies to release branches and after dependency or configuration updates to verify branch health.

The smoke check captures exit codes and isolates the first actionable error from the lint, typecheck, tests, or build steps to guide debugging and reporting.

No specific dependencies are required by the smoke check itself, but your project must have its standard lint, typecheck, test, and build environments configured to execute the validation sequence successfully.

Run the smoke check during tagging, after dependency or configuration updates, or when CI failures require local reproduction. It verifies the current branch before shipping to catch regressions early.