Daily updates from Odoo
Wednesday, June 10, 2026
5 changes · 17.0
Resolved issues and error corrections
This update resolves an issue causing blank content in snail mail documents during validation. The problem stemmed from a recent change that incorrectly used a PDF source. This fix ensures the correct PDF is utilized, resulting in properly formatted mail documents.
Original PR description
This commit fixes a regression introduced in odoo/odoo@dc72061383a4 where, while fixing the calls to actually merge page on a pdf writer instead of the reader, the wrong pdf was used as a source.
This update fixes an error in the VAT balance calculation within the l10n_uy module for Uruguay. The previous formula was inaccurate, leading to incorrect reporting. This change ensures accurate VAT reporting, aligning with local tax regulations.
Original PR description
### Steps to reproduce the issue: 1. Download Accounting and l10n_uy 2. Go to tax report and see the formula of the VAT balance that is incorrect ### Reason to introduce the fix: Correct the formula to display the right amount. opw-6261211 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update fixes an issue where cron workers weren't efficiently managing database connections. By introducing new configuration variables for cron workers, we can now limit their registry usage, reducing memory consumption and improving overall performance. This ensures Odoo runs smoothly under heavy background workloads.
Original PR description
The configuration option `registry_lru_size` does not exist and does not work at all in recent versions. Defining odoo-specific environment variables to handle: - ODOO_REGISTRY_LRU_SIZE: the default registries size - ODOO_REGISTRY_LRU_SIZE_CRON: overwrite for cron workers Cron workers have often a different workload than HTTP workers and we may set a different limit there. If the limit is lower than the number of databases, a cron job will not reuse registries because it cycles through all known ones - in such cases, we can set a lower limit to keep the memory lower. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update resolves a bug that caused a 'divide by zero' error when generating Jordanian e-invoices with invoice lines having a quantity of zero. The fix ensures invoices with zero quantities can now be successfully sent to JoFotara, improving invoice processing reliability. This resolves an issue reported in opw-6262469.
Original PR description
Steps to reproduce: - Ensure Jordanian e-invoicing is installed - Create an invoice where one of the lines has a 0 quantitiy - Send the e-invoice JoFotara (Jordan EDI) Current Behavior: You will get a divide by 0 error popup Expected Behavior: No error and the invoice is sent opw-6262469
Documentation and clarification updates
This update formally includes Djody Kort from Codeforward B.V. in Odoo's contributor legal agreement. This is a standard step for Codeforward contributions and ensures proper licensing compliance. It also prepares for a future bug fix related to server stability.
Original PR description
Adds me (Djody Kort, Codeforward B.V.) to the List of contributors in the existing Codeforward Corporate CLA (`doc/cla/corporate/codeforward.md`, signed by Sander Lienaerts). Prerequisite for an upcoming bug-fix PR to `service/server` — a SIGHUP exit-130 race in `ThreadedServer` under `--dev=reload`. Targeted at 17.0 (the lowest branch the fix applies to) per the CLA signing guide.