Jesse Glick
Jesse Glick
Only partly: https://github.com/vmware-tanzu/velero-plugin-for-gcp/pull/106#pullrequestreview-1540383121
Is this issue solely about `search repo`, or would it apply to other commands which would implicitly look for versions? For example it is unfortunate that if you use, say,...
> …does not work to install the latest version My mistake: it does (#10527), if you take care to ensure that the version string follows SemVer syntax.
@inzanez `helm install`, `helm upgrade`, and other commands work with or without `--version`, so it is richer than just downloading a tarball from a web server, even if incomplete.
Does https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/general-progress-monitoring.md address this issue?
> The actual project uploads don't need this kind of approval Right, after onboarding you just need to securely manage signing & upload keys (pending https://github.com/sigstore/sigstore-maven/issues/12).
BTW there is https://github.com/kruton/jbcrypt which seems to be more recently touched.
Right, currently designed only for 7.2+. Can be retrofitted to work with pre-`ModuleData` releases if people are still building plugins with older baselines.
Also tracked as: https://bugs.launchpad.net/ubuntu/+source/kazam/+bug/1876322
> should be included in the next scheduled feature release Per https://github.com/helm/helm/releases/tag/v3.13.2 > 3.14.0 is the next feature release and [will] be on January 17, 2024. Looking forward to finally...