Rename of OCA modules in the upgrade of odoo.sh

[CRogos]

Not sure if this is the right spot to address this topic, but I couldn't find any information and renaming of OCA module is addressed in OpenUpgrade.

We are using Odoo Enterprise on odoo.sh and therefore using the odoo.sh upgrade process. Nevertheless we also using some OCA modules. One of those is "mass_editing" (15.0) which is now renamed into "server_action_mass_edit" (16.0).
In the OpenUpgrade apriori.py file, the module was added to the "rename" section.

My understanding of OpenUpgrade is that it is covering the Odoo base modules and OCA modules upgrade process. So it is designed to replace Odoo SA upgrade process and not only to extend it by adding support for the OCA modules.

I am now wondering how the OCA module renaming can/should be integrated in our odoo.sh upgrade process.

The only work around I could find, is to add an empty mass_editing module with an manifest dependency on server_action_mass_edit so that mass_editing can be found in the new version and server_action_mass_edit is automatically installed on the upgraded database.