[IMP] Update renamed_models and renamed_fields datasets based on OpenUpgrade

[thienvh332]

• Update the renamed_models and renamed_fields datasets to help odoo-module-migrator detect and handle models and fields that have been renamed between Odoo versions.
• The data is aggregated from OpenUpgrade (upgrade_analysis.txt | pre-migration.py).
  Eg:
  • https://github.com/OCA/OpenUpgrade/blob/18.0/openupgrade_scripts/scripts/account/18.0.1.3/upgrade_analysis.txt
  • https://github.com/OCA/OpenUpgrade/blob/18.0/openupgrade_scripts/scripts/account/18.0.1.3/pre-migration.py

What’s included

• Renamed models

  • Location: renamed_models/migrate_{FROM_VERSION}_{TO_VERSION}/renamed_models.yaml
  • Format: each line → ['old_model_name', 'new_model_name', None]

• Renamed fields

  • Location: renamed_fields/migrate_{FROM_VERSION}_{TO_VERSION}/{module}.yaml
  • Format: each line → ['model_name', 'old_field_name', 'new_field_name', '']

[legalsylvain]

Hi @thienvh332. Thanks for your contribution.

I was asking myself if it's great to have a duplicated data in this project. I mean info in odoo-module-migrator, and info in OpenUpgrade / apriori.py file.

• we could just fetch github and get info parsing apriori.py file. So, odoo-module-migrator is always up-to-date. But, in the meantime, it will not work offline, and that's not great.
• another approach : did you used a script to generate that files ? If yes, maybe you could add it in your PR. (something like update_renamed_models_and_fields_script.py So, we could regularly update the data, based on evolution of the OpenUpgrade project.

A part that point, nice improvment. Thanks !

[thienvh332]

Hi @legalsylvain , Thanks for your comments!

Yes, we used a script to generate those files, and we’ve published it here: OpenUpgrade-Api.
This repository provides a pipeline that pulls data from OpenUpgrade, parses it, and produces the YAMLs consumed by this repo.

Example command to regenerate a YAML:

python manage.py get --object-type removed --object models --versions 18.0 --output-directory output

So whenever OpenUpgrade evolves, the data can be consistently refreshed from the OpenUpgrade-Api repo

Hopefully this proves useful to the community!