Update npm-publish.yml

[kurayami07734]

Publish action would get triggered by release and not by merge to main branch

Changes

Updated the npm publish action such that it publishes after every merge to the main branch

[oleg-nenashev]

Hello, are you sure about that? It basically means switching to continuous delivery. It is totally possible, but in such a case one would need to automatically increment versions and, nice to have, publish changelogs (see Release Drafter in other projects in this org). If you publish like that, it will override the version with new content which is something I would advice against

[kurayami07734]

Hello, are you sure about that? It basically means switching to continuous delivery.

I wanted your opinion on this, actually

I was confused on how I was supposed to create releases

[oleg-nenashev]

As discussed on Slack, I would recommend a pipeline driven by GitHub Releases

1. Changelog Drafter is used to generate draft changelogs
2. Once you are ready to release, you just publish the draft changelog
3. A Release GitHub Action is triggered upon publishing the release, and does the build and deployment for the selected version

See https://github.com/wiremock/python-wiremock for the example