Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Previously supported chart version numbers are now invalid #1738

Open
sa-spag opened this issue Feb 28, 2025 · 3 comments
Open

Previously supported chart version numbers are now invalid #1738

sa-spag opened this issue Feb 28, 2025 · 3 comments

Comments

@sa-spag
Copy link

sa-spag commented Feb 28, 2025

👋 Hello,

Following the upgrade from v1.4.1 to v1.5.0, which includes an update of github.com/Masterminds/semver/v3 from v3.3.0 to v3.3.1, some of our HelmCharts report errors, such as invalid chart reference: validation: chart.metadata.version "32.04.112" is invalid.

See related issue: Masterminds/semver#258.

@stefanprodan
Copy link
Member

32.04.112 is not valid SemVer you can't have 0 suffix, allowing this was a bug in Masterminds/semver.

@sa-spag
Copy link
Author

sa-spag commented Feb 28, 2025

Indeed. Nonetheless, the behavior is not consistent with Helm v3.17.0, which depends on github.com/Masterminds/semver/[email protected].
Note that proper Semantic Versioning support in Helm is being discussed on helm/helm#30513.

@deepakbshetty
Copy link

We are also impacted by this issue.
Vendor private charts albeit with invalid semver that have worked previously are now filtered out in index load. We can flag this to vendor for fix but will only appear in future releases and will take time. As @sa-spag mentiomed, would appreciate consistency with Helm 3.x to use masterminds/semver 3.3.0 as this is a breaking change for many consumers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants