PR State:
merged
PR:
#653
Commit:
7b7f0bbd44d85aa2c4c9b6496e24c9e6ba3b0c04
Merge remote-tracking branch 'origin/18.0' into 19.0
Second continuous forward-port increment (updates PR #653), SHA-preserving.
Absorb 5 new 18.0 commits:
- viin_brand_pos: guard the company service in the POS Navbar favicon patch +
Hoot test (a982703 -> 3c40e2d), made runnable on the branch (5b9ffe0)
- viin_brand_website: adapt the website_background_colorpicker tour to the
branded palette (1722364 -> e0baa1d)
- web_responsive: chatter Log Note disabled-binding + upstream "Action" statusbar
toggler fixes (c676d5a/77a158c) - already present on 19.0, absorbed SHA-only
viin_brand_pos and viin_brand_website stay installable:False (phased-upgrade
posture): the forwarded code and tests land but are not loaded on 19.0.
Fix the Runbot module-graph inconsistency by setting installable:False on three
not-yet-v19-adapted modules that were installable:True on this branch:
- viin_brand_website_slides_forum: new from 18.0; depends on
viin_brand_website_forum, which is installable:False, so the module graph
marked it inconsistent ("some depends are not loaded ... skipped") - the exact
Runbot failure
- viin_brand_auth_signup: new from 18.0, never assessed for Odoo 19
- viin_brand_hr_expense: 18.0 re-enabled it (7fc5f5f) on an 18.0-specific
rationale (white-label, installs clean on 18.0); not v19-verified, so it
returns to installable:False and can be re-enabled individually later
Only web_responsive stays installable:True in the branding cluster, matching the
phased-upgrade posture. Verified on Odoo 19.0 CE: co-installing the core
auto_install triggers (website_slides_forum, hr_expense, auth_signup) plus
web_responsive produces no module-graph inconsistency.
Branch:
19.0