The goal would be to get publishing to NPM set up automatically. I think triggering that from GitHub would require a tag, but then that wouldn't increment the package.jsonversion in the same commit so that'd not be very nice.
Furthermore we should check whether we can / should write back from the action to the repo with a new version. (Or would we just discard the version in the package.json entirely during development and just publish from here?)
The goal would be to get publishing to NPM set up automatically. I think triggering that from GitHub would require a tag, but then that wouldn't increment the
package.json
version
in the same commit so that'd not be very nice.Furthermore we should check whether we can / should write back from the action to the repo with a new version. (Or would we just discard the version in the
package.json
entirely during development and just publish from here?)Related reading: https://medium.com/devopslinks/automate-your-npm-publish-with-github-actions-dfe8059645dd (though the
npm
helpers are no use for us, we need someyarn
ones)