Publish extension task succeeds with error

[jmezach]

I had a setup where I would query the version of an extension and then publish a new version of the extension with a higher version number. However, I deleted the extension from the Marketplace and then ran my release pipeline again. I was expecting the Query Extension Version task to fail, but it actually succeeds. After that, my Publish Extension task was running, but with an incorrect version number. This actually results in the log:

2018-11-02T20:04:20.5406801Z ##[section]Starting: Publish Extension
2018-11-02T20:04:20.5411145Z ==============================================================================
2018-11-02T20:04:20.5411249Z Task         : Publish Extension
2018-11-02T20:04:20.5411368Z Description  : Publish an Azure DevOps extension to the Visual Studio Marketplace
2018-11-02T20:04:20.5411452Z Version      : 1.2.4
2018-11-02T20:04:20.5411563Z Author       : Microsoft Corporation
2018-11-02T20:04:20.5411662Z Help         : 
2018-11-02T20:04:20.5411742Z ==============================================================================
2018-11-02T20:04:21.0657560Z Checking tfx under: /home/vsts/work/_tools/tfx
2018-11-02T20:04:21.0670539Z Found tfx under: /home/vsts/work/_tools/node_modules/.bin/tfx
2018-11-02T20:04:21.0711565Z cfb57f68-5d61-411f-85a5-d8831a46f209 exists true
2018-11-02T20:04:21.0745053Z (node:2968) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Supplied ExtensionVersion must contain a string matching '##.##.##(.##)'.
2018-11-02T20:04:21.0766310Z ##[section]Finishing: Publish Extension

However the task finishes successfully, causing the subsequent Install Extension task to fail since the extension wasn't actually published to the Marketplace. I would expect the Publish extension to fail in this case and my pipeline to abort.

[jessehouwing]

Ahhh another promise rejection... I'll try to fix it.

[jmezach]

Those are fun, aren't they ;).