-
Notifications
You must be signed in to change notification settings - Fork 132
Making a release #219
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Let's add it! Releasing CHP is the same as ~any npm package: npm version $VERSION
npm publish
git push --tags You need an npm account and I can give you access. |
Deal okay I'll learn about that then, I have no experienced on that ;) Push a git tag, build and pusha a docker image, build and publish the npm package. @minrk I created an account called I note that the |
Docker images are tagged and built automatically on docker hub, so should be no need to do anything there. I think those three lines are literally everything in making a release, assuming changelog, etc. are up to date. I've given you write access to the package on npm, so you should be able to publish the next release! |
A release is made now! :) |
Excellent, thank you! |
I'd be very happy to see a release of CHP for z2jh to use. It would allow the z2jh proxy pod to snappily restart following #217 and also allowing the hub pod to become ready a lot quicker without erroring. The hub pod will crash with error unless it has successfully communicated with a running proxy pod that is slow to restart for example.
I'd happily put in some effort here, but could use some initial guidance, approval to work toward making a release, and considerations to have in mind etc.
The text was updated successfully, but these errors were encountered: