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

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

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 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