Closed LeLunZ closed 2 months ago
I think we can also update the engines and dev dependencies in the package.json?
I added another workflow script which is exactly the same as the publish one, except that it can be triggered manually to publish a beta package. I thought this could be useful to publish changes we arent sure about and let someone else test it.
Will merge for now. If the publish-beta script seems useless, we can also remove it later on.
npm publish
see below. But the warning still persists even though its documented like that.@MrAsterisco if these actions are good to go, you need to add your npm token to the repositories secrets. (with the key NPM_TOKEN)