This update refactors the Web Studio module to use a more modern and efficient approach to data handling. Specifically, it utilizes 'contextvars' to manage data within the module, leading to better performance and maintainability. This change improves the underlying code structure without impacting how users interact with Web Studio.

https://github.com/odoo/odoo/pull/256688

This update modernizes how Odoo Enterprise tracks relationships between records using Owl 3's signal system. It replaces older 't-ref' references with the new Owl 3 signals, ensuring compatibility with the latest Odoo version. This change improves the stability and future-proofing of the Enterprise Companion.

## `t-ref` string refs → Owl 3 signals (enterprise companion)

Enterprise side of the Owl 2 → Owl 3 ref-semantics migration. Pairs with the community PR of the same branch name (`master-tref-pr-3-nby`).

### Scope
**Leaf 1** companion — enterprise consumers of the migrated mail/web components.

### Notes
- Rebased onto current enterprise `master` (2026-06-10).
- Community PR: odoo/odoo#269266

This update modernizes how Odoo Enterprise tracks related records by migrating to Owl 3's signal-based referencing system. This change improves the underlying architecture and ensures compatibility with future Owl releases. It primarily impacts components used in the Enterprise Companion.

## `t-ref` string refs → Owl 3 signals (enterprise companion)

Enterprise side of the Owl 2 → Owl 3 ref-semantics migration. Pairs with the community PR of the same branch name (`master-tref-pr-4-nby`).

### Scope
**Leaf 2** companion — enterprise consumers of `AutoComplete` / input hooks.

### Notes
- Rebased onto current enterprise `master` (2026-06-10).
- Community PR: odoo/odoo#269267

This update modernizes how Odoo Enterprise references documents and other data by transitioning to Owl 3's signal system. This change improves the underlying architecture and ensures compatibility with future Odoo releases. It impacts several key modules within the Enterprise edition.

## `t-ref` string refs → Owl 3 signals (enterprise companion)

Enterprise side of the Owl 2 → Owl 3 ref-semantics migration. Pairs with the community PR of the same branch name (`master-tref-pr-5-nby`).

### Scope
**Leaf 3** companion — `documents` `useNestedSortable`, datetime, call-card `useHover` consumers.

### Notes
- Rebased onto current enterprise `master` (2026-06-10).
- Community PR: odoo/odoo#269268

This update modernizes the way Odoo Enterprise tracks signatures by transitioning to Owl 3's signaling system. It improves the underlying architecture for signature requests, aligning with the latest Owl version and ensuring compatibility with future updates. This change primarily impacts the Enterprise Companion module.

## `t-ref` string refs → Owl 3 signals (enterprise companion)

Enterprise side of the Owl 2 → Owl 3 ref-semantics migration. Pairs with the community PR of the same branch name (`master-tref-pr-6-nby`).

### Scope
**Leaf 6** companion — sign `ControlPanel` / `NameAndSignature` adaptation.

### Notes
- Rebased onto current enterprise `master` (2026-06-10).
- Community PR: odoo/odoo#269269

This pull request updates the way attachment previews are handled across several Odoo modules, specifically incorporating a new syntax for OWL 3. This change improves the consistency and reliability of attachment previews within the Enterprise edition, ensuring better functionality for users.

Enterprise counter-part.

task-6255532

https://github.com/odoo/enterprise/pull/118962

This update simplifies how controllers access website-related data. Previously, a function called `get_current_website` was used, which has been replaced with a more direct method leveraging the Odoo environment. This change ensures consistent website functionality across various modules and improves maintainability.

All locations that used `get_current_website` can be replaced in the controllers because `website_id` is automatically present in the `context` for routes with the attribute `website=True`.

This update simplifies invoice processing by merging the `l10n_co_dian` module into the core `l10n_co_edi` module. Additionally, the `l10n_co_edi_mandate` module is also integrated, streamlining the system and reducing complexity. This change improves maintainability and aligns with the primary invoice delivery method.

Since the main, and only, way to send invoice is using dian it only
makes sense to merge the `l10n_co_dian` module into the main
`l10n_co_edi` module.

Since the `l10n_co_edi_mandate` module was only introduced as a separate
module because of stable policy we also merge it into `l10n_co_edi`.

task-5113421

This update refactors the connection between overtime records and employee attendance, improving data accuracy and efficiency. Previously, a workaround was used, but this commit establishes a proper Many2One relationship, aligning with best practices and simplifying future maintenance. This change enhances the reliability of attendance tracking.

In odoo/odoo#241457 we made the relationship between overtime and attendance a m2o
    using time_start and employee_id as keys to attribute an overtime to its attendance.

    This wasn't ideal but was what was possible with the stable policy. In this commit we
    complete that fix by changing the relationship to a proper Many2One.

    task-6172452

This update refactors internal code within several Odoo modules to utilize a new 'plugin' architecture. This change enhances modularity and flexibility, allowing for easier future updates and integrations within the Odoo platform. It primarily impacts the underlying structure of various modules, improving maintainability and scalability.

This update streamlines the Odoo IoT device model by removing redundant information like manufacturer and device subtype. This change simplifies the underlying code, making it easier to maintain and update, which ultimately reduces development time and potential issues.

This commit aims to simplify the IoT device model by removing unnecessary data such as:
- manufacturer,
- device subtype (was only used for printers),

As usual, the goad is to reduce complexity of the
code to improve maintainability.

see odoo/odoo#258127