Release a new version about stackstorm-k8s HOT 11 CLOSED

@mamercad Yes, that's the first step. Don't forget CHANGELOG.md changes before the release.

Then you need to update the https://github.com/StackStorm/stackstorm-k8s/tree/gh-pages index with the new artifact.
I think the https://helm.sh/docs/helm/helm_repo_index/ command is how to do it.
Example: 82c4d56

That could be automated.

from stackstorm-k8s.

This chart is in good shape now.

from stackstorm-k8s.

So a question if you are going to do a version 1 should we consider upgrading the Mongo, RabbitMQ and Redis Helm Charts? There are some breaking changes in those.

I think (I don't have anything other than anecdotal information to back this up) that folks have been running main for a while now? Changing "all of the other things" at this point should be a new issue and new work, I'd argue.

from stackstorm-k8s.

@guzzijones any chance you can take a look at this question?

from stackstorm-k8s.

I believe the process is to update the version in Chart.yaml and push a matching tag. After which it'll eventually be discovered by ArtifactHub. Is that correct @arm4b ?

from stackstorm-k8s.

Maybe as a first pass at this, and, getting it out the door, we add "Releasing information" to the README.md with the steps and get the new version out with it. Are we ready for v1.0.0 at this point?

from stackstorm-k8s.

I know no barriers for v1.0 and the chart is known to be used in production for a long time. @cognifloyd WDYT ?

from stackstorm-k8s.

I've deployed chart-releaser for another project in the past, might be worthwhile for this one as well; I'll snag this issue.

from stackstorm-k8s.

@arm4b 👀 when you have a chance, please.

from stackstorm-k8s.

...we may want to think about an organizational GPG key for signing.

from stackstorm-k8s.

So a question if you are going to do a version 1 should we consider upgrading the Mongo, RabbitMQ and Redis Helm Charts?
There are some breaking changes in those.

from stackstorm-k8s.