domains / families / devops / deploy-pipeline

deploy-pipeline

combined

Run end-to-end deploy pipelines across Stripe, Supabase, and Vercel using the Composio CLI. Promote Stripe products, push Supabase migrations, ship Vercel deployments, and verify with post-deploy checks — all from one script. Triggers a Power Platform Pipeline deployment run for a Power Pages solution. Selects a target stage, validates the package, optionally configures deployment settings (environment variables, connection references), then deploys and polls for completion. Use when asked to: "deploy pipeline", "run pipeline", "trigger deployment", "deploy to staging", "deploy to production", "run power platform pipeline", "deploy solution via pipeline", "promote solution", "push to staging", "push to production".

When to use

• Full-stack product launch that touches billing, database, and frontend together.
• Promoting a preview Vercel build to production with a Stripe price flip and a Supabase migration.
• Weekly release trains where the same sequence repeats and you want it reliable.

When not to use

• Parallel execution across Stripe, Supabase, and Vercel

Skill page

Conflict

The two skills share the name 'deploy-pipeline' but describe entirely different systems and procedures. The first is a Power Platform/Power Pages ALM skill that uses PAC CLI, Azure CLI, and a local pipeline configuration file to promote a solution to a target environment. The second is a full-stack release skill using the Composio CLI to coordinate Stripe, Supabase, and Vercel. They do not overlap in steps, tools, or constraints, so crowning one would hide a real alternative.