publish cannot be ran again of npm publish fails

Question

publish cannot be ran again of npm publish fails

ericclemmons opened this issue 7 years ago · 5 comments

I wasn't logged in, but the changes were committed & tagged, so when running oao release again it said there weren't any changes & failed to publish.

Answer 1 · 2018-05-07T06:13:16.000Z

Oh, that happens to me every once in a while as well. I usually run then npx oao all "npm publish". Maybe that helps you too?

Answer 2 · 2018-05-07T15:25:45.000Z

Thinking about it, maybe oao should check whether you're logged in (npm whoami?) before proceeding with the publish, what do you think?

Answer 3 · 2018-05-07T15:32:51.000Z

That'd be the most side effect way, I think. On May 7, 2018 8:25 AM, "Guillermo Grau Panea" <notifications@github.com> wrote: Thinking about it, maybe oao should check whether you're logged in (npm whoami?) before proceeding with the publish, what do you think? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#78 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAA7TmDCE234IHcCXd60H-lu9ep21SmHks5twGd6gaJpZM4T0Qux> .

Answer 4 · 2018-05-07T16:28:16.000Z

Did you try the workaround I proposed?

Answer 5 · 2018-05-07T17:56:14.000Z

That works!

…

On Mon, May 7, 2018, 9:28 AM Guillermo Grau Panea ***@***.***> wrote: Did you try the workaround I proposed? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#78 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAA7TusYINro3D0kdxvx-2HQ0u4g5uWLks5twHYhgaJpZM4T0Qux> .