You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Hi, I noticed that this repo has not created GitHub tagged releases for all the changes to the helm chart to track the underlying releases of the Temporal server. E.g. the latest commit bumps to v1.18.4 but this does not appear as a GitHub release. Do you intent to only create releases for major versions or is this just a small oversight?
A GitHub release would be preferable as we currently manage packaging the Helm charts in this repository ourselves. With a tag, we can detect new releases, checkout the specific commit, get the version number from the tag, package the chart archive and push to our helm repository.
Describe the solution you'd like
Tag each commit that bumps the Chart's appVersion and image tag of the underlying Temporal server so that it appears as a GitHub release.
Thank you
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Hi, I noticed that this repo has not created GitHub tagged releases for all the changes to the helm chart to track the underlying releases of the Temporal server. E.g. the latest commit bumps to v1.18.4 but this does not appear as a GitHub release. Do you intent to only create releases for major versions or is this just a small oversight?
A GitHub release would be preferable as we currently manage packaging the Helm charts in this repository ourselves. With a tag, we can detect new releases, checkout the specific commit, get the version number from the tag, package the chart archive and push to our helm repository.
Describe the solution you'd like
Tag each commit that bumps the Chart's
appVersion
and image tag of the underlying Temporal server so that it appears as a GitHub release.Thank you
The text was updated successfully, but these errors were encountered: