-
Notifications
You must be signed in to change notification settings - Fork 3
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
add chartpress #7
Conversation
@yuvipanda I think this is ready to review and test. I can't be 100% sure the publishing will work until it's merged. I tried to run it on my fork, but actions just never run there, despite triggers. What do you think about separating chart version from appVersion? I think that really simplifies things, but then we have to pick an initial chart version that's not too confusing. I like to pick an arbitrary offset when things like this happens, like starting with |
@minrk letting them diverge is fine.
Let's do this? You should merge this and iterate as feels appropriate to you! |
After a couple fixes, successfully published kbatch-proxy-0.5.0-0.dev.git.34.h37ac17c. I think we're ready to make an 0.5.0b1 with this and kbatch-dev/kbatch#86 |
Uses chartpress to render the chart on each push to main
The kbatch-proxy image is built here, so it is versioned with the chart, solving kbatch-dev/kbatch#42
With this, making a prelease would be: