NPM token need in repository secrets for publishing packages about barrelsby HOT 4 CLOSED

Thanks @bencoveney !

The publish not triggering seems strange so I'll look into that.
I'll let you know if I need anything else, but that should do it for now.

Thanks again

from barrelsby.

1st release in ~2 years - Well done, and thanks for your contributions 😄

from barrelsby.

Next release diff:
v2.2.0...master

from barrelsby.

Hi @BitForger 👋

I've generated an "Automation" Access Token in NPM and set it up as a secret.

Prior to this I've also been through the old git tags and created a Github release for them where any where missing. I think I had let the github list of releases fall behhind what had been published to NPM. Given that those were release creations, I'm not sure whether you're expecting to have seen a resulting run of the Node.js Package action, but I can't see any triggered.

I've had a look through the changelog and everything looks good. Let me know if there's anything else I can help with to support releasing/publishing a new version.

from barrelsby.