Verify the release, not just the build.

A release-check workflow for routes, public data, metadata, mobile interaction and isolation boundaries.

This guide describes checks. It does not create a workflow in your repository, deploy code or report unperformed tests as passing.

Start with offline regression checks

Test parsing, identity, missing data, known errors and permission boundaries using synthetic fixtures. Remove ambient credentials and block external execution in the offline test process.

Verify the exact hosted target

Confirm the account, environment and version before read-only checks. Verify successful pages, genuine 404s, unavailable features, canonical tags and security headers. A working homepage alone is not complete feature parity.

Check the interactions

Test search, selectors, comparison navigation, keyboard focus, dismissal and mobile overflow. Keep browser observations separate from offline test results. Test error and empty states, not just populated pages.

Record recovery and remaining gates

Keep an identifiable previous release and documented rollback steps. Authentication, customer continuity, source rights, backups and domain cutover require their own evidence and approval. A green build does not authorize production changes.