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
The current Helm chart version, 1.0.1867-DEPLOY-7868dee1-85-1680, doesn't align with our needs. We want to release Helm charts to the customer with a versioning format that makes more sense as part of the release artifacts. The preferred versioning would follow the format 12.1.8.3.{chart_number}.
Please let me know if you need any further inputs to implement this
Thanks
🎤 Pitch / Usecases
The current Helm chart version, 1.0.1867-DEPLOY-7868dee1-85-1680, doesn't align with our needs. We want to release Helm charts to the customer with a versioning format that makes more sense as part of the release artifacts. The preferred versioning would follow the format 12.1.8.3.{chart_number}.
🔄️ Alternative
No response
👀 Have you spent some time to check if this issue has been raised before?
As per our recent discussion, leveraging custom tag should solve the issue: Ref Closing this as not required, feel free to reopen if there's any change in the plan
🔖 Feature description
Hi Team,
The current Helm chart version, 1.0.1867-DEPLOY-7868dee1-85-1680, doesn't align with our needs. We want to release Helm charts to the customer with a versioning format that makes more sense as part of the release artifacts. The preferred versioning would follow the format 12.1.8.3.{chart_number}.
Please let me know if you need any further inputs to implement this
Thanks
🎤 Pitch / Usecases
The current Helm chart version, 1.0.1867-DEPLOY-7868dee1-85-1680, doesn't align with our needs. We want to release Helm charts to the customer with a versioning format that makes more sense as part of the release artifacts. The preferred versioning would follow the format 12.1.8.3.{chart_number}.
🔄️ Alternative
No response
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: