search

paralin / grpc-bus

Call GRPC services (even streams!) from the browser over any two-way socket to Node and soon Go.
MIT License
43 stars 5 forks source link

Document release process #38

Open gabrielgrant opened 7 years ago

gabrielgrant commented 7 years ago

There are a few mentions in the git log of "triggering" a release. What does that consist of? It seems the standard(ish) npm version && npm publish isn't being used directly (there's no version number in the package.json)

Specifically, I'm looking to create a package to test my fix for #35 in downstream projects. For the time being, I've just run npm run build, manually added a version number into the package.json, and then done npm pack. Seems to work, but I'm guessing there's some more straightforward way you're doing this?

Having the info either in the README or as an npm run command would be helpful.

Thanks!

paralin commented 7 years ago

It's semantic-release - when the release branch passes all the tests the travis ci script publishes a release.

paralin commented 7 years ago

Actually I don't have that set up on this repo, I am just manually releasing. Might set it up here.