Promoting npm package by referencing tarball (.tgz) file does not work on Windows build agent

[ghost]

The task fails to promote an npm package by reading data from the package file. It fails when running tar command. It seems the issue is that tar does not like a colon (:) in the full path on Windows.

Probably the solution could be to add --force-local to tar command on windows. See this SO answer.

Task Version

Version: 2.0.4

Task Logs Output

2019-09-20T17:08:21.3894464Z ##[section]Starting: Promote package to Release View
2019-09-20T17:08:21.4011893Z ==============================================================================
2019-09-20T17:08:21.4011944Z Task         : Promote package to Release View
2019-09-20T17:08:21.4011970Z Description  : Promotes a package to a Release View in VSTS Package Management
2019-09-20T17:08:21.4012023Z Version      : 2.0.4
2019-09-20T17:08:21.4012049Z Author       : Rene van Osnabrugge
2019-09-20T17:08:21.4012073Z Help         : Version: 2.0.4. [More Information](https://github.com/renevanosnabrugge/vsts-promotepackage-task/wiki)
2019-09-20T17:08:21.4012098Z ==============================================================================
2019-09-20T17:08:22.7048810Z Promoting package(s) by reading metadata from package file(s) matching pattern '**/*.tgz' from root directory 'D:\a\r1\a\'
2019-09-20T17:08:23.3757665Z Matching paths found:
2019-09-20T17:08:23.3757828Z D:\a\r1\a\build-drop\package\package-name-0.2.8.tgz
2019-09-20T17:08:26.6568212Z ##[error]tar (child): Cannot connect to D: resolve failed
2019-09-20T17:08:26.6808279Z ##[section]Finishing: Promote package to Release View

Task Configuration Screenshot

[ghost]

Updated the issue with task version:
Version: 2.0.4

[rroman81]

so is this integrated into latest release?