whop-deploy

To automate Whop app deployment from preview to production, run the deployment command in your current working directory. The script validates your repository HEAD against the last deployment state and handles the transition using the audited whop-state-mcp tool.

For automated Whop app deployment, you need an existing adopted Whop app repository and a valid .whop-pipeline.json file. The process validates that your current repository HEAD differs from the lastDeploy.sha recorded in the pipeline configuration.

Yes, Whop deployment automation works without manual intervention. It handles the entire deployment process including status collection and finalization automatically, while reporting detailed information about the deployment status and handling errors gracefully.

Your Whop app deployment may not proceed if the repository HEAD matches the lastDeploy.sha in your .whop-pipeline.json file. The automation validates that there are actual changes to deploy before initiating the preview to production transition.

The best way to move an adopted Whop app to production is using the automated whop.deploy command. It streamlines the transition by validating repository changes, collecting status, and finalizing the deployment without requiring manual steps.

Deployment status reporting for Whop apps works by collecting detailed information throughout the deployment process using the whop-state-mcp tool. It handles errors gracefully and reports comprehensive status details upon finalization of the preview to production transition.