[Feature] Custom versioning support about helm HOT 3 OPEN

Helm does follow semver. Which that does mean you can use a prerelease version e.g. --version 1.2.3-{short_commit_hash}.{build_number}.{timestamp}

Semver is important, as it is often necessary to sort chart versions. e.g. install the latest version of a chart. And so Helm chart versions are not arbitrary strings like e.g. docker image tags.

from helm.

its great that helm follows semver, but having a prerelease version is not appropriate for a lot of internal projects and in a lot of cases (like ours) makes naming of our dynamic feature environments very clunky.

For instance, why should I need to prepend a version to the start of my chart name, if the production version is going to change 15+ times while the feature is developed?

Would you consider at the very least the addition of a parameter to override the default behavior?

from helm.

Helm does follow semver. Which that does mean you can use a prerelease version e.g. --version 1.2.3-{short_commit_hash}.{build_number}.{timestamp}

Semver is important, as it is often necessary to sort chart versions. e.g. install the latest version of a chart. And so Helm chart versions are not arbitrary strings like e.g. docker image tags.

I understand that, but in the same time why restrict others to use the version they want for their internal purposes.
The whole point is not about changing helm mechanism from semver to what docker does, but just allow ppl to use their custom versioning (just remove error when you try to package helm with your custom version and try to install it with exact version specified in install command).

from helm.