[MIG] docsource: mark no-DB-layout-change core modules Nothing to do#99
Open
dnplkndll wants to merge 1 commit into
Open
[MIG] docsource: mark no-DB-layout-change core modules Nothing to do#99dnplkndll wants to merge 1 commit into
dnplkndll wants to merge 1 commit into
Conversation
9e083b9 to
00375e4
Compare
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.
00375e4 to
3eddcd8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
--updatescope and from the coverage count.
Why these are safe
Confirmed by a source-level model/field diff (odoo/odoo
18.0vs19.0) acrossall 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. Raisesthe fork's marked-module coverage to 584/632.