[19.0][MIG] base_user_role_company: Migration to 19.0

[tishmen]

Scope

• base_user_role_company only

Summary

• Migrate to Odoo 19.0 following OCA guide.
• Override parent unique constraint with company-aware one: UNIQUE(user_id, role_id, company_id).
• Tests aligned with 19.0 (group_ids API).

Pre-commit

• Verified locally; no additional changes applied beyond auto-fixes.

Temporary dependency

• Added a temporary reference in root test-requirements.txt to install base_user_role from the PR ref, per OCA guidelines.

Tests

Command:

./odoo/odoo-bin -c odoo.conf -d bur19_tests_burco -i base_user_role,base_user_role_company --test-enable --test-tags "/base_user_role_company" --without-demo=all --log-level=info --stop-after-init

Result: green locally.

Depends on:

• [19.0][MIG] base_user_role: Migration to 19.0 #382

[tishmen]

Depends on #382.

Temporary dependency

• Added a temporary reference in test-requirements.txt to install base_user_role from [19.0][MIG] base_user_role: Migration to 19.0 #382 (per OCA wiki above). This commit will be removed after the base PR merges.

Highlights

• Unique constraint overridden to UNIQUE (user_id, role_id, company_id).
• Company‑aware role enablement honored via active_company_ids.
• Local tests green. Command used:

./odoo/odoo-bin -c odoo.conf -d bur19_tests_burco -i base_user_role,base_user_role_company --test-enable --test-tags "/base_user_role_company" --without-demo=all --log-level=info --stop-after-init

Maintainers ping

• @dreispt (module), @sebalix @jcdrubay @novawish (base visibility).

Kept as draft until #382 is approved/merged; can flip to ready on request.

[much-filipe-colaco]

@tishmen I attempted to install this migrated version of base_user_role_company on a local instance of Odoo 19.0. The installation seemed to work, but trying to access the home page the error below is logged.
Python version: 3.12.3

2026-01-28 18:11:34,490 282 ERROR dummy odoo.http: Exception during request handling. 
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/odoo/http.py", line 2785, in __call__
    response = request._serve_db()
               ^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/odoo/http.py", line 2268, in _serve_db
    raise self._update_served_exception(exc)
  File "/usr/lib/python3/dist-packages/odoo/http.py", line 2266, in _serve_db
    return service_model.retrying(serve_func, env=self.env)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/odoo/service/model.py", line 184, in retrying
    result = func()
             ^^^^^^
  File "/usr/lib/python3/dist-packages/odoo/http.py", line 2313, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/odoo/http.py", line 2435, in dispatch
    return self.request.registry['ir.http']._dispatch(endpoint)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/odoo/addons/base/models/ir_http.py", line 357, in _dispatch
    result = endpoint(**request.params)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/odoo/http.py", line 788, in route_wrapper
    result = endpoint(self, *args, **params_ok)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/odoo/custom/addons/base_user_role_company/controllers/main.py", line 17, in web_load_menus
    del response.headers["Cache-Control"]
        ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
AttributeError: __delitem__

I looked at alternative solutions and found that the following option works (source).

    def web_load_menus(self, lang=None):
        # v19 signature: (lang=None). Keep behavior of disabling menu HTTP cache.
        response = super().web_load_menus(lang=lang)
        # Remove Cache-Control header to disable menu HTTP caching
        # Using .pop() as Werkzeug Headers no longer supports __delitem__ (del)
        response.headers.pop("Cache-Control", None)
        return response

[andreschenkels]

@tishmen I believe the base_user_role is in the main repo for v19 can you change this PR so the tests can run and thus this PR can be validated?