Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[18.0][MIG] sale_purchase_force_vendor: Migration to 18.0 #2523

Open
wants to merge 23 commits into
base: 18.0
Choose a base branch
from

Conversation

jaydeep32
Copy link

No description provided.

victoralmau and others added 23 commits January 22, 2025 10:31
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: purchase-workflow-14.0/purchase-workflow-14.0-sale_purchase_force_vendor
Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-14-0/purchase-workflow-14-0-sale_purchase_force_vendor/
…time so that it is always displayed and apply the correct domain in both use cases

TT39679
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: purchase-workflow-14.0/purchase-workflow-14.0-sale_purchase_force_vendor
Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-14-0/purchase-workflow-14-0-sale_purchase_force_vendor/
Currently translated at 100.0% (11 of 11 strings)

Translation: purchase-workflow-15.0/purchase-workflow-15.0-sale_purchase_force_vendor
Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-15-0/purchase-workflow-15-0-sale_purchase_force_vendor/es/
@jaydeep32 jaydeep32 changed the title 18.0 mig sale purchase force vendor [18.0][MIG] sale_purchase_force_vendor: Migration to 18.0 Jan 22, 2025
@jaydeep32 jaydeep32 mentioned this pull request Jan 22, 2025
32 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.