Upgrade path from v1 addon

[jelhan]

Is the upgrade path for existing v1 addons created with default Ember CLI addon blueprints defined already? Or should we hold back migrating existing addons still for some time?

I'm primarily interested in migrating addons to v2 format which aren't that actively maintained. This is not an early adopter case. Churn should be minimized. But I hope that after all experiments with @embroider/addon-blueprint this new blueprint is now stable. Is that expectation correct?

[mansona]

so the plan is that we are going to have a codemod (similar to the ember-vite-codemod) that can guide you through the upgrade path from both v1 addons and the @embroider/addon-blueprint to this one.

This one is intended to become the default but there is an RFC process that needs to happen first 👍

[TSenter]

so the plan is that we are going to have a codemod (similar to the ember-vite-codemod) that can guide you through the upgrade path from both v1 addons and the @embroider/addon-blueprint to this one.

This one is intended to become the default but there is an RFC process that needs to happen first 👍

Is there any kind of timeline on that codemod? No rush obviously, just curious what to expect/look forward to.