Skip to content

[MIG] docsource: mark no-DB-layout-change core modules Nothing to do - #99

Open
dnplkndll wants to merge 1 commit into
19.0from
19.0-mig-core-noschema
Open

[MIG] docsource: mark no-DB-layout-change core modules Nothing to do#99
dnplkndll wants to merge 1 commit into
19.0from
19.0-mig-core-noschema

Conversation

@dnplkndll

@dnplkndll dnplkndll commented May 31, 2026

Copy link
Copy Markdown

Flips the docsource status of 71 core modules from blank to Nothing to do.
These have no DB layout change between 18.0 and 19.0, so they need no migration
script — but a blank status excluded them from the migration test's --update
scope and from the coverage count.

Why these are safe

Confirmed by a source-level model/field diff (odoo/odoo 18.0 vs 19.0) across
all 71: no model/table rename, no stored-field removal/rename/type change, no new
required stored field. This corroborates the analysis bot's pre-existing
No DB layout changes. note already present in each row's notes column.

Predominantly country l10n_* packs and payment/POS/connector modules. Raises
the fork's marked-module coverage to 584/632.

AI-assisted (Claude Code); every change reviewed, tested, and owned by the author.

@dnplkndll
dnplkndll force-pushed the 19.0-mig-core-noschema branch 2 times, most recently from 00375e4 to 3eddcd8 Compare June 5, 2026 19:54
@dnplkndll
dnplkndll force-pushed the 19.0-mig-core-noschema branch 4 times, most recently from f4040a9 to 5e91b02 Compare June 19, 2026 11:59
@dnplkndll
dnplkndll force-pushed the 19.0-mig-core-noschema branch 6 times, most recently from c901c8a to 13a0aff Compare August 5, 2026 15:21
@dnplkndll
dnplkndll force-pushed the 19.0-mig-core-noschema branch 2 times, most recently from 19ecead to 447678f Compare August 6, 2026 17:37
These 71 core modules carry no schema change between 18.0 and 19.0 — the
status column is now flipped from blank to Nothing to do so they are covered
and included in the migration test scope. Confirmed by a source-level
model/field diff (no model/table rename, no stored-field removal/rename/retype,
no new required stored field); corroborates the analysis bot's existing
"No DB layout changes." notes on each row.
@dnplkndll
dnplkndll force-pushed the 19.0-mig-core-noschema branch from 447678f to 4013f4a Compare August 7, 2026 14:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant