Odoo Changelog — 2025-10-20

Monday, October 20, 2025

3 changes · 19.0

Improvements(3)

Enhancements to existing features

[IMP] base: Removing ZIP code requirement for Peru

Core19.0base

Peruvian customer addresses no longer need a ZIP code to be accepted. This better reflects local address practices in Peru and reduces unnecessary data entry friction for customers and staff.

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#zip-code

[IMP] core: mitigate RPC error during chrome shutdown

PR #232299

Core19.0core

This update makes automated browser shutdown more reliable when Chrome reports rare errors during test cleanup. It helps prevent unfinished test environments and zombie builds, improving stability of the development and release pipeline.

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

[IMP] mail: use link plugin in composer

PR #97666

Enterprise19.0mailai

Links added in the mail composer are now recognized and highlighted more reliably. This improves message clarity for users and also simplifies the underlying editor setup to reduce duplicated configuration.

Original PR description

This commit enables the link plugin in the mail composer so that the link will be properly parsed and hightlighted.

This commit also improves the plugin set and clean up the duplicated plugin lists.

task-5172795
backport - https://github.com/odoo/enterprise/pull/97504
https://github.com/odoo/odoo/pull/232347

#mail#composer#links#editor

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

This commit enables the link plugin in the mail composer so that the link will be properly parsed and hightlighted. This commit also improves the plugin set and clean up the duplicated plugin lists. task-5172795 backport - https://github.com/odoo/enterprise/pull/97504 https://github.com/odoo/odoo/pull/232347