0.0.5 pending release from upcoming bug fixes

[justmike1]

Company or project name

Seemplicity

Use case

Releases

Describe the solution you'd like

Hey team, I am refreshing daily the releases page to see when 0.0.5 is released because I see some bugs we had have been fixed. ( didn't raise an issue and checked first the closed / PRs section )

Just wondering if you have some calendar release cycle or it's pretty much when accumulated enough fixes, etc.

I would suggest to add CI/CD so every merge to main will incur patch version bump if it's possible.

Describe alternatives you've considered

No response

Additional context

No response

[ashishch432]

The helm chart and operator image is published on every main commit.

[justmike1]

I don't understand I see here: https://github.com/ClickHouse/clickhouse-operator/blob/main/dist/chart/Chart.yaml version 0.0.1 and here: https://github.com/ClickHouse/clickhouse-operator/releases 0.0.4 and for sure there was new updates after 0.0.4 ( almost a month ago ), what should I do then?

[justmike1]

I typically go by releases page ( also as a reference for automatic bumps )

[ashishch432]

Check out
https://github.com/orgs/ClickHouse/packages/container/package/clickhouse-operator
https://github.com/orgs/ClickHouse/packages/container/package/clickhouse-operator-helm

[justmike1]

ok I believe the current CI/CD you have for internal use case is great and common, like what we have internally for some of our tools.
But as an open-source first product we will need semantic version releases / tag releases ( scanners will be able to catch version changes ).

In general I see you already did that, not sure if manual or not, but specifically 0.0.5 is an outlier.

[GrigoryPervakov]

I don't understand I see here: https://github.com/ClickHouse/clickhouse-operator/blob/main/dist/chart/Chart.yaml version 0.0.1 and here: https://github.com/ClickHouse/clickhouse-operator/releases 0.0.4 and for sure there was new updates after 0.0.4 ( almost a month ago ), what should I do then?

The actual version is set in the chart during the packaging
https://github.com/ClickHouse/clickhouse-operator/blob/main/Makefile#L209

[justmike1]

so expectations from users of this helm chart is to package the helm locally?

[GrigoryPervakov]

so expectations from users of this helm chart is to package the helm locally?

You can use a package that is built on every commit, as @ashishch432 mentioned.
It has a valid semver tag, but with a bit flipped semantics, it uses the latest released version instead of the next version to release.

Just wondering if you have some calendar release cycle or it's pretty much when accumulated enough fixes, etc.

Currently, we do not have a calendar, just releasing when "enough" changes have accumulated since the previous one.