All heroku commands on Windows exit with code 1 on success

[toolness]

trafficstars

Hello, I'm on Heroku CLI 7.16.0 using Windows 10 and it seems like all Heroku commands exit with status code 1 even when they succeed using git bash, e.g.:

$ heroku maintenance:on
Enabling maintenance mode for ⬢ tenants2... done
$ echo $?
1

Or:

$ heroku container:push -R
... stuff happens ...
Your image has been successfully pushed. You can now release it with the
'container:release' command.
$ echo $?
1

This might be a more general case of #955. In any case, it makes automating things with the CLI not terribly reliable.

[toolness]

Hey, this seems to have been fixed at some point between 7.16.0 and 7.16.6! So I'll close this issue.

[jdx]

We didn't change anything

[thierry2015]

This should be reopened since the issue is still occuring.

Heroku CLI: 7.19.4 NodeJS: 11.3.0 Windows: 10 x64

[frederikhors]

Please re-open this. It's still broken!

[Ezequiel-MO]

Hello - I'm Feb 28th, 2024, and this is still happening ? It's confusing I updated my heroku

$ heroku update heroku: Updating CLI from 8.7.1-3f5e369 to 8.10.0-25f0948... done

and then ...

$ heroku container:login echo $? Login Succeed 1

[justinwilaby]

Reopening this here instead of maintaining a duplicate over at Oclif.

[k80bowman]

Internal work item

[tcfprobus]

Under heroku cli 10.0.0, running commands in bash under windows returns "0" when successful. After updating to 10.12.0, I'm getting return values of "1" for the same commands, which terminates my bash script. It's deja-vu all over again.