Odoo Changelog — 2025-10-20

Monday, October 20, 2025

3 changes · saas-18.4

Improvements(3)

Enhancements to existing features

[IMP] base: Removing ZIP code requirement for Peru

Coresaas-18.4base

Peruvian customer records no longer require a ZIP code, reflecting that ZIP codes are not commonly used in Peru. This makes customer data entry easier and helps avoid unnecessary validation issues for Peruvian addresses.

Original PR description

As ZIP codes are not widely used in Peru, the requirement for a ZIP code to be provided for a Peruvian customer should not be present.

task-5012593


---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#223157

#Peru#addresses#customer data

[IMP] iot_drivers: avoid auto register event for terminals

PR #232282

Coresaas-18.4iot_drivers

Payment terminals connected through Odoo IoT will no longer be automatically registered for event handling, because they already manage their own events. This reduces unnecessary background handling and aligns terminal behavior with devices that send events independently.

Original PR description

As for printers that can send event whenever they want, payment terminals handle event themselves.

We then removed auto event registering for payment terminals.

odoo/enterprise#97617

#iot#payment terminals#events

[IMP] core: mitigate RPC error during chrome shutdown

PR #232283

Coresaas-18.4core

This change makes Odoo's automated test browser shutdown more robust when Chrome reports rare shutdown errors. It helps prevent stuck test builds and lingering browser processes, improving runbot reliability without affecting normal users.

Original PR description

In some instances, Chrome can apparently fail CDTP calls with "Execution context was destroyed". According to the internet this mostly happens because of navigation events, here it's not clear if…

In some instances, Chrome can apparently fail CDTP calls with "Execution context was destroyed". According to the internet this mostly happens because of navigation events, here it's not clear if this is in response to `stop`-ing the page, or a pre-existing navigation directive interfereing with the stop-ing of the browser. I tried reproducing locally under the assumption that the `Page.stopLoading` might be the cause but got nowhere[^1].

This issue seems extremely infrequent, and in most cases is but a minor annoyance, an error appears on the corresponding build, and that's it.

However if the error occurs during `ChromeBrowser.stop` then the browser is not terminated, which on runbot prevents the docker image from shutting down properly, and leaves zombie builds.

Therefore make `ChromeBrowser.stop` more resilient to errors in the initial section so that we do terminate the browser even if the "graceful CDTP shutdown" fails. While at it, add a fallback to kill the browser if it does not terminate gracefully.

https://runbot.odoo.com/odoo/error/233442

[^1]: and the error only happening in 18.0 and later when `Page.stopLoading` was present long before that makes it likely the proximal cause is in the code being run, especially as all the errors sampled from the builds list are related to pos and the failure are immediately preceded by ongoing HTTP requests

Forward-Port-Of: odoo/odoo#232222
Forward-Port-Of: odoo/odoo#232060

As ZIP codes are not widely used in Peru, the requirement for a ZIP code to be provided for a Peruvian customer should not be present. task-5012593 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#223157

In some instances, Chrome can apparently fail CDTP calls with "Execution context was destroyed". According to the internet this mostly happens because of navigation events, here it's not clear if this is in response to `stop`-ing the page, or a pre-existing navigation directive interfereing with the stop-ing of the browser. I tried reproducing locally under the assumption that the `Page.stopLoading` might be the cause but got nowhere[^1]. This issue seems extremely infrequent, and in most cases is but a minor annoyance, an error appears on the corresponding build, and that's it. However if the error occurs during `ChromeBrowser.stop` then the browser is not terminated, which on runbot prevents the docker image from shutting down properly, and leaves zombie builds. Therefore make `ChromeBrowser.stop` more resilient to errors in the initial section so that we do terminate the browser even if the "graceful CDTP shutdown" fails. While at it, add a fallback to kill the browser if it does not terminate gracefully. https://runbot.odoo.com/odoo/error/233442 [^1]: and the error only happening in 18.0 and later when `Page.stopLoading` was present long before that makes it likely the proximal cause is in the code being run, especially as all the errors sampled from the builds list are related to pos and the failure are immediately preceded by ongoing HTTP requests Forward-Port-Of: odoo/odoo#232222 Forward-Port-Of: odoo/odoo#232060