Thursday, January 29, 2026
5 changes · 17.0
Enhancements to existing features
This update addresses issues with the Belarusian accounting chart of accounts (COA) by removing duplicate account types and streamlining data management. The changes ensure more accurate and efficient accounting processes within the Odoo system.
Original PR description
- Currently, l10n_id COA has unacceptable account types for some accounts - There are also duplicate accounts since data for such accounts exists in chart template, but Odoo also creates for them Task-[5360134](https://www.odoo.com/odoo/project.task/5360134?debug=assets) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
This update fixes an error that occurred when users attempted to view the BoM Overview after archiving warehouses. The fix ensures the system correctly handles scenarios where all warehouses are archived, preventing a technical error and ensuring the BoM Overview functionality remains available.
Original PR description
Currently, an error is encountered when a user tries to open the BoM Overview when all warehouses are archived. **steps to Reproduce:** - Install MRP without demo - Archive the warehouses from the inventory configuration - Now create a BOM from MRP/products and try to open the overview **Error:** `IndexError: list index out of range` **Root Cause:** When the user clicks on BoM Overview, the system tries to fetch all warehouses at [1]. At [2], the system tries to fetch all active warehouses, and since they are archived, we get a traceback here. [1]- https://github.com/odoo/odoo/blob/a8fdf26ee138b1f71e0534cbef73efd95bb2445d/addons/mrp/report/mrp_report_bom_structure.py#L114 [2]- https://github.com/odoo/odoo/blob/a8fdf26ee138b1f71e0534cbef73efd95bb2445d/addons/mrp/report/mrp_report_bom_structure.py#L21-L22 **Solution:** This commit prevent error by ensuring that all the warehouses are available for computation at [2]. sentry-**6379275060**
This update resolves a confusion for users of the account_peppol module. Previously, a user setting ('proxy_client_user') was configured as 'demo' while another ('edi_mode') was set to 'test'. This change ensures both settings are consistently configured, improving clarity and usability for users.
Original PR description
Currently, the proxy_client_user is neutralized as demo. But the edi_mode is set to test. It's confusing for the users, and we should be consistent. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update ensures that WebGL testing continues to function correctly in Chrome's headless mode (version 144+). Chrome's default settings now disable WebGL, so this change re-enables it for testing purposes, specifically to maintain functionality for website builder features. While SwiftShader is less secure, it's deemed acceptable for controlled test environments.
Original PR description
Since Chrome 144 disabled [^1] by default the WebGL fallback to the software renderer SwiftShader, this commit reenables [^2][^3] it when running in headless mode to allow to keep testing WebGL features (i.e. image filters in website builder). Note: the SwiftShader implementation is considered deprecated and less safe than proper hardware based ones, hence not recommended for a regular usage with untrusted content. However, as tests are run in a more controlled environment, it looks reasonnable to opt-in to keep actually testing WebGL features. [^1]: https://chromium-review.googlesource.com/c/chromium/src/+/7128438 [^2]: https://issues.chromium.org/issues/476172421 [^3]: https://chromestatus.com/feature/5166674414927872
This update corrects a technical issue where expired sales leads were triggering warning messages. The change ensures that a single record ID is used, resolving a previous error in how the system processed payment link data. This prevents the warning and ensures proper functionality.
Original PR description
### Issue: In #244061 changes, the expired so leads to warning message. However, the batch `res_id` is used instead of single record which is an error. opw-5478691