Continously release current version as ts-protoc-gen@next about ts-protoc-gen HOT 4 CLOSED

OK, I've made some progress on this, however I am going around in circles and would appreciate some guidance :)

After following this guide, I've modified our .travis.yml to add a deploy step which successfully performs an npm publish --tag=next each time master builds.

This works great, however on successive builds of master the publish step fails with the following error:

npm ERR! publish Failed PUT 403
npm ERR! code E403
npm ERR! You cannot publish over the previously published versions: 0.7.0-pre. : ts-protoc-gen

I'm guessing I need to 'bump' the version in our package.version but I'm unsure how to do this; sure I cloud use something like standard-version to achieve this, but won't this result in an inifinite loop each time I commit the bumped package version? 😕

from ts-protoc-gen.

Ah ok, I was just overthinking this. Taking inspiration from the Typescript package and use the datestamp as a unique suffix on the package version, no need to commit it into the repository

from ts-protoc-gen.

Ok this is now done from a CI and release script level. Just need to update the README (and maybe the changelog) to mention that you can install prereleases using the @next tag

from ts-protoc-gen.

Done

from ts-protoc-gen.