Successful balena deploy reports release commit rather than release id

[nazrhom]

A successful balena deploy should report the release id alongside the commit used by the release. Release ID is usually needed to interact with a release that was just created by a deploy (e.g. tag it)

• balena CLI version: e.g. 11.2.1 (output of the "balena version" command) 11.7.2

[thgreasi]

If it's just for tags, then we have two other issues that predate this one. See: https://github.com/balena-io/balena-cli/issues/1060 See: https://github.com/balena-io/balena-cli/issues/1064

Also WRT managing tags using release commit hashes, this was recently added in the latest balena-sdk. See: https://github.com/balena-io/balena-sdk/blob/master/CHANGELOG.md#1270---2019-07-15

[pdcastro]

Note: the balena push --detached command appears to have the opposite problem (prints only the release ID, not commit), that could be improved at the same time:

$ ./bin/balena push test-nuc -s ~/simple_container --detached
Build successfully started
  Release ID: 1619809

[myarmolinsky]

Update: semver is what we should report now