-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
[prometheus-kube-stack] Failed to publish 42.0.0 in ghcr #2719
Comments
@scottrigby could you have a look please? |
Ping, there is a lot of unpublished releases now, I had to go back at page 6 in releases to find the latest one published in ghcr. And other users have concerns about this |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
Still appears to be an issue |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
Still here, latest published release is from November 2022. |
This issue is being automatically closed due to inactivity. |
Describe the bug a clear and concise description of what the bug is.
Hello, the CI still fails to publish new charts in ghcr.
From the list of published versions we can see that the latest stable version is 41.7.4; which means that we missed: 41.8.0, 41.9.0, 41.9.1 and 42.0.0.
What's your helm version?
NA
What's your kubectl version?
NA
Which chart?
kube-prometheus-stack
What's the chart version?
42.0.0
What happened?
No response
What you expected to happen?
No response
How to reproduce it?
No response
Enter the changed values of values.yaml?
No response
Enter the command that you execute and failing/misfunctioning.
NA
Anything else we need to know?
No response
The text was updated successfully, but these errors were encountered: