Christophe Simonis
Christophe Simonis
upgradeci retry with always only hr
In order to catch all potential issues: upgradeci retry with all modules in all versions (that will take a while...)
This looks wrong. It doesn't handle the case of replacement of different length, for example a removed related. `partner_id/.id` become `parent_id/partner_id/.id` Or even, just `.id` Can you please add a...
In dev mode, don't install it and just point the odoo's `--upgrade-path` to the `src` directory.
Actually, there is a real bug in the odoo/upgrade#6690 PR: the temporary table hasn't been cleaned up by the upgrade script (due to the early return check).
upgradeci retry with always only base
No, this is wrong. You only disable rules that have an XMLID. Can you please link to the failing request?
This is wrong. We deactivate those rules because they may refer to fields defined by custom modules (even if they don't have a xmlid). We must deactivate all custom rules....
upgradeci retry with always only documents
Indeed, it should not be automatically determined. A `noupdate:bool | None = None` attribute can be added to the function.