How to publish updates on this repo

[leovujanic]

For maintainers, we should add a description how to publish new package versions.

Maybe we can define team based responsibilities here?

[krukru]

Great idea. We already have a readme with steps - we can just add the two extra steps here. I am not sure but I think running npm version patch and npm publish will be enough, provided that you are logged in to npm registry and your account is linked to degordian repo

[jakagacic]

I have tested this simple flow and it works, if you have the right permissions at npm. If not, ping @bonzzy

Edit: as of now, you can also ping me 🥇

[krukru]

@leovujanic we have setup jenkins to publish other private npm modules. Would you be ok that Jenkins publishes automatically for you when merging into master, but it is the authors responsibility to provide a correct version increment (it won't build if the version in package.json stays the same)

[leovujanic]

@krukru it's fine with me and every shape of automation is welcome.
I figured out how to publish npm package, but I think that would be better to have that procedure documented here for feature reference. Now when we intensively working on js modules everyone knows how to do it, in the feature the one will need to google or ping someone how to do it. Also, there were cases with different versions of master and the published package. I believe that that was a consequence of not defined procedure. And what about publishing to npmjs.org, can we define some rules, e.g. at least one person needs to review your code etc.
I believe that there is a lot of space for improvements in terms of documentation, not only on this repo.