The retransmission of the authentication token to the server providing
the artifact caused the following errors when using Artifacts v4:
HTTPError: Response code 400 (Authentication information is not given
in the correct format. Check the value of Authorization header.)
It looks like the service serving the artifacts does not expect the
authentication header, and therefore complaines about inproper use of
the authentication header. Delegating the redirect-handling to the `got`
library fixes the issue according to my tsts.
got@v12.x has a dependency on @sindresorhus/is@v5.x and it uses optional chaining operator "?.".
Probably due to issue https://github.com/vercel/ncc/issues/873 this syntax got into our dist/index.js. For some unknown reason it results in error when action is executed in GitHub runner despite the node version is 16.17.