Thursday, October 9, 2025
7 changes · 19.0
Enhancements to existing features
Payslips that were previously shown as “Validated” will now appear as “Done”. This aligns the payslip status wording with the related payrun status, making payroll screens more consistent for users.
Original PR description
If the payslip status is "validated", the display status for the payslip is "Validated". The display has been changed to "Done" to match with the payrun's status.
The Stripe payment code was reorganized to keep related checkout and payment form behavior in the same area. This is an internal improvement that should make future payment updates easier to maintain without changing the customer payment experience.
Restaurant point-of-sale demo data now shows selected products with colors that differ from their categories. This helps customers see during onboarding that product colors can be customized independently, making menu setup easier to understand.
Original PR description
In this commit: ------------------ - We’ve added random colors to the below products in onboarding to help customers understand that they can choose different colors for products than the selected pos category. ### Products assigned new colors: - Water - Green Tea - Fanta - Bacon Burger - Pasta 4 Formaggi - Chicken Curry Sandwich - Club Sandwich - Sushi Lunch Combo task: 5103944
The point of sale product editor now shows the name of a color variant when users hover over it. This makes it easier for staff to identify the correct product option quickly and avoid confusion when colors look similar.
Original PR description
In this commit: --------------- - We will display variant names when hovering over them from edit product popup on UI for color variants. task: 5095570
The bank configuration card now uses an adjusted background color when dark mode is enabled. This improves visual consistency and readability for users configuring online bank synchronization in dark mode.
Original PR description
This commit will change the background color of the dark mode of the configure bank cart. no task id
Odoo's core memory cleanup settings were adjusted to match changes in Python 3.13 and 3.14. This helps keep the system aligned with newer Python behavior and supports stable performance as the platform evolves.
Original PR description
The thresholds were changed in 3.13: threshold0 = 2000 instead of 700 There are only 2 collections instead of 3 since 3.14 and the second collection is processed incrementally. https://github.com/python/cpython/blob/3.14/InternalDocs/garbage_collector.md --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update reorganizes how the Accounting app decides when a journal entry needs confirmation before validation. It keeps the same user experience while making future customizations easier and less costly to maintain.
Original PR description
## Description of the issue/feature this PR addresses: This PR refactors the `action_validate_moves_with_confirmation` method to improve its extensibility. Currently, the conditions that determine…
## Description of the issue/feature this PR addresses: This PR refactors the `action_validate_moves_with_confirmation` method to improve its extensibility. Currently, the conditions that determine whether an `account.move` requires a confirmation dialog before posting (e.g., future-dated moves) are hardcoded within the action method itself. This design limits extensibility, as customizing the confirmation criteria requires overriding the entire action. This approach leads to code duplication and increases the maintenance burden for custom modules. To address this, the validation logic is decoupled and extracted into a new, protected helper method: `_get_moves_requiring_confirmation`. This change improves the modularity of the `account` module and provides a clean extension point for developers, without altering the existing user-facing behavior. ## Current behavior before PR: The logic for identifying moves that require confirmation is tightly coupled with the `action_validate_moves_with_confirmation` method. Customizing these conditions necessitates a complete override of the method, which is not ideal for maintainability. ## Desired behavior after PR is merged: The confirmation logic is isolated in a new, dedicated `_get_moves_requiring_confirmation` method. This provides a clear and standard extension point, allowing developers to modify the confirmation criteria by simply overriding this new method. This promotes cleaner code, reduces duplication in custom modules, and improves overall maintainability. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr