Closed jnsvd closed 2 years ago
Hi @jnsvd We released a new version v1.0.6 with a fix for the above issue. Please test and let us know if you are still facing the issue.
PS - v1 is now pointing to v1.0.6 so the above workflow requires no changes.
@t-dedah I confirm the fix is working, thank you for the fast response!
We're getting the following output in the pipeline run logs since
v1.0.5
is released:When using previous version
1.0.4
(by configuringuses: azure/CLI@1.0.4
) no such errors are observed and the build is completing successfully.