Use npm to publish package

[pplancq]

The github action you set up https://github.com/pascalgn/npm-publish-action/blob/master/Dockerfile uses version 12 of node with yarn 1.

So I wonder if yarn isn't causing the problem because it's used by default.

So I've configured it to use npm as you were able to use it locally without any problems, which should work, or so I hope.

I'm really sorry for all the problems, it's the first time that using husky has caused me problems.

As a last resort we could temporarily remove husky until we find a permanent solution.

[bencompton]

Still no luck. NPM is rate limiting it now for some reason: npm ERR! 429 Too Many Requests - PUT https://registry.npmjs.org/jest-cucumber. I initially thought this was because I fired off 2 workflows in quick succession, but it still produces the same error after waiting 30 minutes.

No worries about the issues--it might be something to do with pascalgn/npm-publish-action like you said. I was just trying to get something working quickly and didn't take the time to properly vet it. I'm good with focusing on semantic-release instead of spending more time on this if you'd prefer, since running npm publish locally works fine in the meantime.

[pplancq]

I understand, I'll see if I can find you a simple solution to release faster and more efficiently.
Just to make sementic-release work properly could you just add a git tag v4.0.10 on your last commit.
I'll finish my pr #200 with commitlint and then I'll propose a clean workflow with semantic-release.
I don't mind, I like to mess around with workflows.

[bencompton]

I'm grateful for all of your efforts help modernize and streamline this project, and looking forward to your next PR!