bump to rc.3 once released about helm-2to3 HOT 7 CLOSED

The call to cfg.Releases.Create on line 97 may migrate a Helm 2 release as the older Helm 3 metadata. That might not be compatible with Helm 3.0. I'll have to check and confirm just to be 100% sure, but in any case I wanted to reach out. In either case, updating to rc.3 will remove any doubts :)

from helm-2to3.

sure

from helm-2to3.

@bacongobbler This is should not be a breaking change for the plugin. No changes are required.

FYI, we would always update to the latest release of Helm 3 in any case.

from helm-2to3.

I will update once RC-3 is released.

from helm-2to3.

It was identified from helm/helm#6881 (comment) that this may not actually be a backwards-incompatible change. Phew!

from helm-2to3.

In middle of something at moment but will try and get to it shortly. Off hand, should be ok. Will check shortly. Thanks for reaching out @bacongobbler

from helm-2to3.

@bacongobbler Following testing, it works as expected. This is because the plugin interfaces with the Helm object field name definitions and not the persisted object field names. It would only be affected if the Helm object definitions changed and/or relevant API changed.

from helm-2to3.