Potential regression caused by #110 about action

[Andarist]

For my own reference:
failed job
successful job

[Andarist]

It indeed seems like the check for the authToken has failed for some reason. I'm not yet sure how because what you put there seems to match the regexp. My bet is that you have additional whitespace at the beginning of your line with the token and thus the ^ in the regexp prevents that from matching. I thought that the leading whitespace was not allowed there.

Could you check if that is the case?

[emmenko]

Yes you're right, there are indeed whitespaces

[Andarist]

Ok, great - and I assume this is allowed since u were using it successfully before.

Could u prepare a PR with a fix for that? Just add "any amount of whitespace" after ^ in the regexp. I could then release it from mobile by merging the PR cause im not at the computer right now

[emmenko]

Sure, I can adjust the regex. Thanks for the help!

[emmenko]

Btw, do you think this is also related to the actual JSON.parse error? 🤔

[Andarist]

It might be - my guess is that its failing on parsing the authentication error there since it ends up in the stderr but we only try to parse stdout. Different npm versions put errors in either stdout or stderr - which is super inconvenient for us to handle.

I plan to rework how we publish packages this week (or next week) and I will take a look at solving this too.

[emmenko]

@Andarist alright, I created a PR with the fix and some refactoring.

[Andarist]

Fixed by #116