Hello 馃憢
Actually, the project was tagged with v0.11.0 (yesterday / 2019-10-11).
But the chart version is yet in v0.11.0-beta.0 (2019-10-03).
https://hub.helm.sh/charts/jetstack/cert-manager
Thanks for all guys!
/kind bug
Small ping amazing @munnerz :)
How strange - I can see the chart was published fine. I鈥檒l see if I can kick something in the hub/our chartmuseum!
Thanks a lot 馃檹
@munnerz do you have some news about that?

I have been looking into this - I'm not sure what's going on as the chart's .tgz has been published to our GCS bucket just fine.
Digging further in.. we are also serving this from our chart repository just fine too:
$ curl https://charts.jetstack.io/index.yaml
apiVersion: v1
entries:
cert-manager:
- appVersion: v0.11.0
created: "2019-10-10T13:57:16.097Z"
description: A Helm chart for cert-manager
digest: 41826c830da91f45c816931707c05736766e4014c579d29b9def46fa211e9d30
home: https://github.com/jetstack/cert-manager
icon: https://raw.githubusercontent.com/jetstack/cert-manager/master/logo/logo.png
keywords:
- cert-manager
- kube-lego
- letsencrypt
- tls
maintainers:
- email: [email protected]
name: munnerz
name: cert-manager
sources:
- https://github.com/jetstack/cert-manager
urls:
- charts/cert-manager-v0.11.0.tgz
version: v0.11.0
So perhaps this is a Helm Hub bug?!
Commented here: https://github.com/helm/hub/issues/165#issuecomment-542096155
Now to try and find a Helm Hub admin 馃槃
Big thanks 馃檹
A curiosity question: what the software do you use for your Chart Museum? chart museum?
Yep, chart museum running on GKE 馃槃.
FWIW, you should still be able to install the v0.11.0 version of the chart right now by specifying --version=v0.11.0 - I think this issue exclusively effects the Helm Hub UI exclusively.
Thanks for the tips.
Thanks for the tricks.
Enjoy! It's ok :)
This is now fixed 馃槃