Odoo Changelog — 2026-06-18

Thursday, June 18, 2026

5 changes · master

Refactoring(5)

Code cleanup and technical improvements

[REF] ai: remove useComponent

PR #119131

Enterprisemasteraccount_reportsknowledge

This update removes outdated and easily replaceable 'useComponent' elements across several Odoo modules. This refactoring streamlines the codebase and improves maintainability. The changes primarily affect the account reports and knowledge modules, ensuring a cleaner and more efficient system.

Original PR description

Remove some useComponent that can easily be replaced.

Task-6268109

PR community: https://github.com/odoo/odoo/pull/267742

#maintenance#code cleanup

[REF] iot: use OWL3 prop validation

PR #120860

Enterprisemasteriot

This update modernizes the IoT module by transitioning to a new standard for defining component properties (OWL3). Unused prop definitions related to a reporting component have also been removed, streamlining the module's structure and reducing complexity.

Original PR description

This commit changes all the props definitions in the IoT module to the new OWL3 style. It also removes the prop definitions for the `IoTReportLocalStorage` component, as the props are never used.

#iot#prop validation#modernization

[REF] account,*: multi ID - remove company_registry

PR #115838

Enterprisemasteraccountl10n_ae_fafl10n_at_saftl10n_be_intrastataccount_saftMEDIUM

This update streamlines how partner identifiers are managed within Odoo, consolidating them into a single JSON field. Removing the outdated 'company_registry' field and standardizing routing identifiers improves compatibility with e-invoicing standards like UBL and Peppol, simplifying reporting and integration. This change enhances data accuracy and reduces complexity for users.

Original PR description

We previously replaced the scattered, country-specific partner
identifier fields with one JSON field `additional_identifiers`.
This commits continues to clean up after that change, mainly:

- Move the additional_identifiers JSON field into base: some modules
(l10n_xx_hr_payroll) don't depend on `account` yet still have similar
contact's identifiers.
- Drop the company_registry field as now, everything should be more
specific, and stored in the JSON field.

Smaller changes:
- add base helpers selecting a partner's preferred legal-entity, tax and
routing identifier, reused by UBL/CII EDI, SAF-T and Peppol/PDP
- rename peppol_eas/peppol_endpoint to routing_scheme/routing_endpoint
(+ computed routing_identifier) so any e-invoicing network can route
using this fields => less confusing.
- Some countries have non-stored compute/inverse for convient access
(l10n_fr_siret/siren, SG UEN, NO Brønnøysund, ...),
- adapt UBL/CII exports, SAF-T reports and invoice reports after the
removal of the company_registry.
- cleanup of the scheme/endpoint validation so that's it's more coherent. There
was 3 different validation before, of only a subset of schemes.

task-6140750

#e-invoicing#reporting#UBL#Peppol#identifiers

[REF] website: use a controller to get current website instead of orm

PR #120829

Enterprisemasterwebsite

This update refactors how Odoo determines the current website, moving from a database query to a controller-based approach. This change enhances efficiency and stability by avoiding reliance on the original `website` model method. The update improves the underlying data retrieval process.

Original PR description

The corresponding community PR adds a controller
`/website/get_current_website_id` to get the current website.

This commit uses it instead of the `website` model's method `get_current_website`.

#website#performance#data

[REF] website: Use self.env.website and remove get_current_website

PR #120560

Enterprisemasterwebsitebase

This update simplifies website routing by replacing older methods with a more reliable approach. It ensures that website-specific data is consistently accessed, leading to improved accuracy and stability. Future work will address more complex fallback scenarios.

Original PR description

[REF] base/website: migrate controllers and models to `self.env.website` Replaced legacy `get_current_website()` calls with `self.env.website` across controllers and models where fallback behavior…

[REF] base/website: migrate controllers and models to `self.env.website`

Replaced legacy `get_current_website()` calls with `self.env.website` across controllers and models where fallback behavior was unintended.

Mechanics & Context:

- For routes defined with `website=True`, the routing layer automatically injects `website_id` into the context.
- `self.env.website` natively reads this `website_id` from the context, behaving exactly like `get_current_website(fallback=False)` (without falling back to `host_id` or the first available website).
- `host_id` (added during routing) represents the website matched strictly by domain name, independent of `website=True` or website-module specific overrides.

Scope of Cleanup:

This PR intentionally focuses only on the call sites that can be safely converted to a plain `self.env.website`. Locations that require explicit fallback handling, such as falling back to `host_id` (the strict domain-matched website) or a default website, have been left out of this pass when it's linked to a complex feature or behavior. They require deeper analysis and will be addressed in a subsequent PR.

#website#routing#performance

We previously replaced the scattered, country-specific partner identifier fields with one JSON field `additional_identifiers`. This commits continues to clean up after that change, mainly: - Move the additional_identifiers JSON field into base: some modules (l10n_xx_hr_payroll) don't depend on `account` yet still have similar contact's identifiers. - Drop the company_registry field as now, everything should be more specific, and stored in the JSON field. Smaller changes: - add base helpers selecting a partner's preferred legal-entity, tax and routing identifier, reused by UBL/CII EDI, SAF-T and Peppol/PDP - rename peppol_eas/peppol_endpoint to routing_scheme/routing_endpoint (+ computed routing_identifier) so any e-invoicing network can route using this fields => less confusing. - Some countries have non-stored compute/inverse for convient access (l10n_fr_siret/siren, SG UEN, NO Brønnøysund, ...), - adapt UBL/CII exports, SAF-T reports and invoice reports after the removal of the company_registry. - cleanup of the scheme/endpoint validation so that's it's more coherent. There was 3 different validation before, of only a subset of schemes. task-6140750

[REF] base/website: migrate controllers and models to `self.env.website` Replaced legacy `get_current_website()` calls with `self.env.website` across controllers and models where fallback behavior was unintended. Mechanics & Context: - For routes defined with `website=True`, the routing layer automatically injects `website_id` into the context. - `self.env.website` natively reads this `website_id` from the context, behaving exactly like `get_current_website(fallback=False)` (without falling back to `host_id` or the first available website). - `host_id` (added during routing) represents the website matched strictly by domain name, independent of `website=True` or website-module specific overrides. Scope of Cleanup: This PR intentionally focuses only on the call sites that can be safely converted to a plain `self.env.website`. Locations that require explicit fallback handling, such as falling back to `host_id` (the strict domain-matched website) or a default website, have been left out of this pass when it's linked to a complex feature or behavior. They require deeper analysis and will be addressed in a subsequent PR.