Thursday, December 18, 2025
4 changes · 19.0
Enhancements to existing features
The security policy now lists Odoo 19.0 as a supported version. This helps customers and partners understand that the latest release is covered by Odoo's security support process.
Original PR description
Adding version 19.0 in the supported versions of the SECURITY.md file.
The Malaysian e-invoicing screens now show MyInvois information more clearly on partner records. The MyInvois tab is also hidden when it is not relevant, reducing clutter on journal entries outside sales and purchases.
Original PR description
This commit: - Fixes alignment of the `MYINVOIS INFORMATION` section on the partner form. - Hides the `MyInvois` tab on journal entries where journal type is neither `sale` nor `purchase`. task-5356808 Forward-Port-Of: odoo/odoo#240333 Forward-Port-Of: odoo/odoo#239837
A new automated test checks that the connection between a purchase order and its related repair order remains available after the purchase order is confirmed. This helps prevent regressions that could make it harder for users to navigate between purchasing and repair workflows.
Original PR description
Add a test to verify that the smart link PO <-> RO does not break after the PO is confirmed. opw-5121816
This update enhances the delivery of Guatemalan electronic invoices to customers by automatically attaching the XML file alongside the PDF. Previously, only the PDF was sent, but now customers receive both files directly in their email, improving transparency and convenience. The XML file naming convention has also been standardized.
Original PR description
Purpose: In the Guatemalan localization, when an electronic invoice is created, the email template to the customer already contains the PDF version of the DTE. However, the XML file, generated and…
Purpose: In the Guatemalan localization, when an electronic invoice is created, the email template to the customer already contains the PDF version of the DTE. However, the XML file, generated and sent to the SAT through Infile, is not attached to that email. Even though the SAT and Infile deliver the XML to the customer, it is more convenient and transparent if Odoo includes it directly in the outgoing invoice template email, so the customer receives both files in one place. Before this commit:- - Only PDF version is attached by default in customer email for e-invoices. - Name of edi document is prefixed with `Demo` if company is in demo environment (check parent company's environment in case of child company) (e.g. DEMO_certificate_INV_2025_00001.xml) and prefixed with `SAT` if company is in testing or production environment(e.g. SAT_certificate_INV_2025_00001.xml). After this commit:- - XML version is also attached by default along with PDF in customer email for e-invoices. - Name of edi document is always prefixed with `SAT`. task-5224521 Forward-Port-Of: odoo/enterprise#98978