New release breaks builds, stalls forever on attempt to use.

[duaneking]

We had a pipeline working a few days ago on Mac on a private runner (We cant use github hosted mac runners because GitHub doesnt scale well for chromium browser builds) with this using the newest version, and as of today after the update it no longer installs and just spins its wheels and does nothing for as long as it is allowed to time out if the step is used. No debug output, nothing just a process that sits doing nothing before it dies.

You broke your actions release in the newest update, please fix it.

And please add some kind of unit test or something so you can test your code before releasing it on production.

[duaneking]

Extracted the raw logs from the runner; your not checking for existence of files before attempting to overwrite them and your not using the prompt correctly, you broke so many peoples builds, this is unacceptable.

##vso[task.debug]agent.TempDirectory=undefined ##vso[task.debug]agent.workFolder=undefined ##vso[task.debug]loading inputs and endpoints ##vso[task.debug]loaded 0 ##vso[task.debug]Agent.ProxyUrl=undefined ##vso[task.debug]Agent.CAInfo=undefined ##vso[task.debug]Agent.ClientCert=undefined ##vso[task.debug]Agent.SkipCertValidation=undefined ##vso[task.debug]Agent.ProxyUrl=undefined ##vso[task.debug]Agent.CAInfo=undefined ##vso[task.debug]Agent.ClientCert=undefined ##vso[task.debug]check path : /Users/runner/actions-runner/_work/_actions/digicert/ssm-code-signing/v1.0.0/build/lib1.json ##vso[task.debug]adding resource file: /Users/runner/actions-runner/_work/_actions/digicert/ssm-code-signing/v1.0.0/build/lib1.json ##vso[task.debug]system.culture=undefined usecase called for installation is keypair-signing using path /var/folders/xq/lm5llfv52gj0jrvtr_znvw000grgn/T Tool to be downloaded and used {} and url is {} smctk-apple-any signingmanager/api-ui/v1/releases/noauth/smctk-apple-any/download ##vso[task.debug]APIKey=undefined file after write 624890 tool is in a zip file trying to extract it /var/folders/xq/lm5llfv52gj0jrvtr_znvw000grgn/T/DigiCert One Signing Manager Tools/smtools-mac-x64.zip Extracting archive ##vso[task.debug]testing directory '/var/folders/xq/lm5llfv52gj0jrvtr_znvw000grgn/T//DigiCert One Signing Manager Tools/' ##vso[task.debug]which 'unzip' ##vso[task.debug]found: '/usr/bin/unzip' ##vso[task.debug]/usr/bin/unzip arg: /var/folders/xq/lm5llfv52gj0jrvtr_znvw000grgn/T/DigiCert One Signing Manager Tools/smtools-mac-x64.zip ##vso[task.debug]exec tool: /usr/bin/unzip ##vso[task.debug]arguments: ##vso[task.debug] /var/folders/xq/lm5llfv52gj0jrvtr_znvw000grgn/T/DigiCert One Signing Manager Tools/smtools-mac-x64.zip /usr/bin/unzip /var/folders/xq/lm5llfv52gj0jrvtr_znvw000grgn/T/DigiCert One Signing Manager Tools/smtools-mac-x64.zip Archive: /var/folders/xq/lm5llfv52gj0jrvtr_znvw000grgn/T/DigiCert One Signing Manager Tools/smtools-mac-x64.zip replace DigiCert SSM Signing Clients/DigiCert-EULA_Signing Manager (5.29.20).rtf? [y]es, [n]o, [A]ll, [N]one, [r]ename:

So it looks to me like you guys are using the wrong arguments in your CLI commands, and you guys didn't even test this.

[duaneking]

The above output is for the older version that was the most recent release until a few hours ago; This shows that we are not able to revert back to an older version due to this issue, either.

[duaneking]

The above is evidence that even the newest version does not work due to this unwanted prompting.

[duaneking]

@vishalshanbhag-digicert Please fix this it has made it unusable

[vishalshanbhag-digicert]

The concerned issue is resolved in v1.1.0 (digicert/ssm-code-signing@v1.1.0). Please update to this version.

For more details on this version, please refer Here

[duaneking]

I don't trust the new version because the notes make it clear that you removed features we need to keep.

Please sync with Ben.