deployctl deploy ignores the --prod option

[ansipunk]

After deploying with said command, upon visiting the Deno Deploy's dashboard, it can be seen that no deployment is set as a production environment. When visiting the production website, its responds with "404 - The requested deployment does not exist."

Users have to manually promote an environment to production through the dashboard. deployctl deployments redeploy --prod fails saying that the project does not have a production environment and preview environment's ID has to be manually set in order to actually promote.

[ansipunk]

To make matters worse, deployctl deploy --prod demotes the last production deployment, but doesn't promote any new deployments.

[theTechGoose]

+1

[arnauorriols]

The bug happens when using the flags --env-file or --env. Working on a fix now.

[arnauorriols]

@ansipunk @theTechGoose Can you confirm you are using either of --env-file or --env flags? Check also the deno.json config file, they might be defined there.

[arnauorriols]

@ansipunk @theTechGoose v1.13.1 is out. Please test it and let us know if the issue is fixed in your end.

[ansipunk]

@arnauorriols yup, fixed now. I indeed was using --env-file, never tried without it.