-
Notifications
You must be signed in to change notification settings - Fork 398
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
Problem if appVersion is decimal #705
Comments
What is your helm version and the BTW I do not think it is the issue about CM 🤔 . |
I tried with Hem 3.12.0 - 3.12.2. I agree, that this may be a Helm issue. If so, I apologize for creating this issue. |
@markusheiden it would also be good to know what version of ChartMuseum you are seeing this happen with. I did some testing locally and I can't seem to reproduce with the latest ChartMuseum release + Helm 3.12. #290 also looks related. |
Per my knowledge , I think the real |
@cbuto I experienced the problem with the GitLab chart registry. To my knowledge they use ChartMuseum (at least we use |
I tried to reproduce the issue by uploading different styles of Sorry for taking your time. |
Since 2023-07-15 18:00 (timezone most probably CEST)
helm repo add --force-update --username gitlab-ci-token --password ${CI_JOB_TOKEN} ${CI_PROJECT_NAME} ${CI_API_V4_URL}/projects/${CI_PROJECT_ID}/packages/helm/stable
(according to https://docs.gitlab.com/ee/user/packages/helm_repository/) does no longer work against the GitLab package registry that uses ChartMuseum to my knowledge.Error: looks like "https://gitlab.com/api/v4/projects/34739132/packages/helm/stable" is not a valid chart repository or cannot be reached: error unmarshaling JSON: while decoding JSON: json: cannot unmarshal number into Go struct field ChartVersion.entries.appVersion of type string
To me, this looks like the JSON generated from our
Chart.yaml
is wrong. ExampleChart.yaml
from our repo (last successful deployment):Here the
appVersion
may be a valid decimal number instead (because int representations are a a subset of hex representations). Maybe using that value for generating JSON without escaping in the decimal case causes the problem?The downloaded
index.yaml
looks correct. I wonder where JSON comes into play here at all?The text was updated successfully, but these errors were encountered: