Portal and public users can now upload, download, and remove pending attachments directly from the website chatter, making customer-facing discussions more complete without backend access. The invoice portal chatter is also shown inline below invoices and its layout is adjusted for easier use.

Description of the issue/feature this PR addresses:
task id -
https://www.odoo.com/web#id=37264&action=327&model=project.task&view_type=form&menu_id=
Current behavior before PR:

Desired behavior after PR is merged:




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

Accounting fiscal position rules can now handle postal code ranges that include letters, not just numbers. This improves localization support for countries such as Canada, where postal codes are alphanumeric, helping taxes and fiscal rules apply more accurately.

Task: https://www.odoo.com/web#id=1948120&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720
pad: https://pad.odoo.com/p/r.89d59b0033b0f57e50e3b9e53adc2082

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:

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

This change refreshes internal performance test benchmarks for the mail testing area so they match the current application behavior. It also reorganizes shared test setup to keep the test code easier to maintain, with no expected impact on end users.

Customers buying courses can now choose between adding a course to their cart or buying it immediately when that option is enabled. The change also prevents course-selling features from being automatically reinstalled, giving businesses more control over whether they sell eLearning content online.

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




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

Decimal precision handling is now built into Odoo’s base system instead of relying on a separate module. This simplifies maintenance and lets core models such as currencies use shared precision rules while keeping older custom code working with warnings.

The decimal precision feature makes sense to be an ORM feature, no need to be
in a specific module.
The limitation was also that models like res.currency were not able to use a
decimal precision as this was raised at #19668 

Keep a backward-compatible signature with a warning.
    
Task id: 48198
Closes odoo/odoo#25467

The QWeb template documentation now marks several older loop helper variables and integer loop usage as deprecated. This helps developers avoid relying on rarely used shortcuts that can be calculated directly, reducing future maintenance risk.

These variables aren't used in Odoo and can be easily computed
anyway.

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




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

Product attribute lines are now created in batches, reducing the time needed to process large numbers of products. This improves performance for product catalog setup and updates, with reported processing time reduced by about 30% in the tested scenario.

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




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

When a serial number is entered for a tracked product in stock quantity or inventory adjustment screens, the quantity is now automatically set to one. This reduces manual entry and helps prevent quantity mistakes for individually tracked items.

On quant view, when you set serial number for a tracked product, its quantity is automatically set on 1.

Task #2025397

EasyPost shipping requests now include the product HS code when available. This helps improve customs documentation accuracy for international deliveries and reduces the risk of shipping delays caused by missing classification details.

Before the fix, we didn't send the hs code to the easy post API. 
Added the HS code to easypost.
Task id: 1964479

This update adapts several business apps to a shared system setting for decimal precision, replacing older module-level setup. It keeps calculations and displayed numeric values consistent while simplifying maintenance across payroll, manufacturing, quality, rental, subscription, and invoicing features.

<b> Task: </b> https://www.odoo.com/web?#id=48198&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720
<b> Pad:</b> https://pad.odoo.com/p/r.b7203e0259fe5f6c20fb86a7abad9f21

Community PR odoo/odoo#25467

Partner profile images that are taller than they are wide will no longer be squeezed into a square. This keeps contact photos looking accurate and more professional in partner records.

**Partner images with greater height than width gets stretched into a square.**

Issue: When you choose an image of a partner whose height is greater than it's width,
it gets stretched into a square.

After this PR is merged, partner image will be prevented from being squeezed and stretched into a square.

Task Link:
https://www.odoo.com/web#id=1982082&action=327&model=project.task&view_type=form&menu_id=4720

Pad Link: https://pad.odoo.com/p/r.8563a0edc34dfef5c2467d2d654c3bdc

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

This fix ensures that saved list and kanban views respect their configured default order, even when a favorite filter is used. It also prevents the order from unexpectedly changing when users open a record and return via breadcrumbs, making navigation more predictable.

In a list/kanban view when applying a default_order on the view,

Before this commit,
 1) The default_order was not applied to the view
 2) when default_order applied, Click on an element of the list/kanban and
    then go back to the list/kanban with the breadcrumbs. So, default_order
    has been changed.

This is because the wrong value was passed because of an insufficient check
to determine the orderedBy for the loadparams.

After this commit,
 1) default_order will be applied to the view
 2) default_order will not be changed when going back through breadcrumbs

Description of the issue/feature this PR addresses:
1) The default_order was not applied to the view
2) when default_order applied, Click on an element of the list/kanban and
    then go back to the list/kanban with the breadcrumbs. So, default_order
    has been changed.

Current behavior before PR:
1) The default_order was not applied to the view
2) when default_order applied, Click on an element of the list/kanban and
    then go back to the list/kanban with the breadcrumbs. So, default_order
    has been changed.

Desired behavior after PR is merged:
1) default_order will be applied to the view
2) default_order will not be changed when going back through breadcrumbs

Issue: 
https://www.odoo.com/web#id=1922576&action=327&model=project.task&view_type=form&menu_id=4720

Pad:
https://pad.odoo.com/p/r.4cbd1001c8d7b423f182da52fe8da959

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

This update removes an outdated internal coding pattern across many Odoo apps and replaces it with the current recordset-based approach. It prepares the platform for removal of deprecated framework behavior, improving maintainability and reducing the risk of unexpected developer-facing behavior without introducing a direct business workflow change.

Adapt all code that was using `api.one` to recordset-style method and
remove any and all calls to `api.one` in preparation for its removal.

Related to https://github.com/odoo/enterprise/pull/3277

Inventory adjustments that are still in draft or have been cancelled can now be deleted. This keeps stock records easier to clean up when adjustments are no longer needed, without affecting completed inventory changes.

This update removes use of an outdated internal programming pattern across several Odoo Enterprise apps and adapts the code to the newer recordset approach. It prepares the system for future platform changes while keeping existing business features working as expected.

Adapt all code that was using `api.one` to recordset-style method and
remove any and all calls to `api.one` in preparation for its removal.

Related to https://github.com/odoo/odoo/pull/29511