Manifest Version Mismatch
A finding from the Migration Audit that flags a version entry in __manifest__.py that may not match the target Odoo version.
What This Finding Means
The version string in __manifest__.py does not align with the target Odoo version. The convention places the Odoo major version at the start of the string, and a stale prefix signals the module was last maintained for an older release.
Why It Matters
A mismatched version prefix can confuse upgrade tooling and the module catalog, and it often indicates that the module has not been reviewed for the target release. The depends list deserves the same scrutiny, since dependencies can be removed or renamed between versions.
Old Odoo Example
{
'name': 'My Module',
'version': '14.0.1.0.0',
'depends': ['base', 'sale'],
}When migrating to Odoo 18, the version should become '18.0.1.0.0'.
Target Version Risk
- Upgrade tooling misreading the module version
dependsreferencing modules removed or renamed in the target version
Recommended Fix Direction
Update the version prefix to match the target Odoo major version while keeping your own module revision suffix. Review every entry in depends and confirm each dependency still exists under the same name in the target version.
How to Verify Manually
Open __manifest__.py and confirm the version prefix matches the target release. On a clean target database, attempt to install the module and confirm every dependency in depends resolves.
Related Odoo Doctor Tool
The Manifest Audit reads your __manifest__.py and reports version and dependency details to review against the target release.