Approval-gated Vercel deployment promotion workflow. It reads the project and target deployment, lists current aliases for context, then promotes exactly one deployment through recued-core.vercel.deployment.promote. It never creates deployments, rolls back, pauses projects, mutates domains or environment variables, deletes records, or calls arbitrary Vercel APIs.

How it works 15 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (15 steps)

■ project_id_trim trim

Trim whitespace from setting project id

■ deployment_id_trim trim

Trim whitespace from setting deployment id

■ team_id_trim trim

Trim whitespace from setting team id

■ team_slug_trim trim

Trim whitespace from setting team slug

■ reason_trim trim

Trim whitespace from setting reason

■ has_project compare

Check if project id trim has data

■ has_deployment compare

Check if deployment id trim has data

■ ready all

Check if all conditions are true

■ project ?

■ deployment ?

■ aliases_raw ?

■ promote ?

skip: step.ready not_equal true

■ aliases default

Apply default

■ alias_count count

Count items in aliases

■ card to_summary

Format results as a summary card

Settings 6 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

reason setting =

vercel setting =

team id setting =

team slug setting =

project id setting =

deployment id setting =