chore: release v15 - #56651
Merged
Merged
Conversation
…ng Voucher Adds a `pcv_job_timeout` Int field (default 3600s) to Accounts Settings so admins can tune the enqueue timeout for PCV background jobs without a code change. All three `frappe.enqueue` calls in `process_period_closing_voucher.py` now read this value at runtime. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> (cherry picked from commit 13b6c4a) # Conflicts: # erpnext/accounts/doctype/accounts_settings/accounts_settings.json
(cherry picked from commit 3da7eef) # Conflicts: # erpnext/accounts/doctype/accounts_settings/accounts_settings.json # erpnext/accounts/doctype/accounts_settings/accounts_settings.py # erpnext/patches.txt
…-56417 refactor: configurable timeout on process pcv (backport #56417)
…-55191 refactor(sales_person_wise_transaction_summary): Replace SQL with que… (backport #55191)
….utils.bold` on company deletion prompt (#56441)
…ccounts (cherry picked from commit 37ec2d0)
(cherry picked from commit 548d90d)
…-56497 fix: handle missing serial and batch bundle in print format (backport #56497)
…-56460 fix: remove frappe.utils from jinja context in process statement of accounts (backport #56460)
…-15-hotfix/pr-56497 Revert "fix: handle missing serial and batch bundle in print format (backport #56497)"
The Quality Inspection Parameter DocType did not have `allow_rename` enabled, so the "Rename" action was hidden from the form's menu (the 3-dots / ⋮ options). Since the DocType is auto-named from the `parameter` field (`autoname: field:parameter`), users had no way to correct or change a parameter's name once created. Enable `allow_rename` so users can rename a Quality Inspection Parameter from the form menu. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> (cherry picked from commit adfef48) # Conflicts: # erpnext/stock/doctype/quality_inspection_parameter/quality_inspection_parameter.json
…-56127 fix: allow rename for Quality Inspection Parameter (backport #56127)
(cherry picked from commit b9f5a77)
…-56559 fix: remove dead bundle helper call from purchase receipt print format (backport #56559)
fix: reserve projected stock for production plan based on BOM qty
…#56568) (#56618) fix: carry item-level project to Purchase Receipt GL entries (#56568) Purchase Receipt stock and asset GL lines used the item row's cost center but always fell back to the document-level project, unlike Purchase Invoice which uses the item-level project. add_gl_entry accepted a project argument but never wrote it to the GL dict, so the inward, Stock Received But Not Billed, landed cost, divisional loss, sub-contracting and exchange rate lines dropped the row's project. Write project into the GL dict and pass project=item.project on the entries that were missing it, so project behaves like cost center and matches Purchase Invoice. Ticket: 72523 (cherry picked from commit 6f97c71) Co-authored-by: Jatin3128 <140256508+Jatin3128@users.noreply.github.com>
…Postgres DISTINCT)
rfq_transaction_list had two defects introduced when it was converted to the query
builder:
1. `party.supplier == party[0]` compared supplier to a column literally named "0"
(a stray index on the DocType, not the intended `parties[0]` value). This renders
as `supplier = \`0\`` / `supplier = "0"` and errors on BOTH engines
(MariaDB: Unknown column '0'; Postgres: column "0" does not exist), so the
supplier portal RFQ list was completely broken.
2. SELECT DISTINCT ordered by `creation`, which is not in the select list. Postgres
rejects this ("for SELECT DISTINCT, ORDER BY expressions must appear in select list").
Compare against `parties[0]` and add `creation` to the select list.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
(cherry picked from commit a7d9078)
# Conflicts:
# erpnext/controllers/tests/test_website_list_for_contact.py
…-56231 fix(controllers): fix supplier-RFQ portal list query (wrong column + Postgres DISTINCT) (backport #56231)
…pt has no bundle (backport #56631) (#56645) fix(stock): value batch/serial return from ledger when original receipt has no bundle (#56631) * fix(stock): value batch/serial return from ledger when original receipt has no bundle * test(stock): add test to validate the valuation of serial/batch for return when original receipt has no bundle (cherry picked from commit 6184c05) Co-authored-by: Sudharsanan Ashok <135326972+Sudharsanan11@users.noreply.github.com>
frappe-pr-bot
requested review from
mihir-kandoi,
rohitwaghchaure and
ruthra-kumar
as code owners
June 30, 2026 10:39
github-actions
Bot
added
skip-release-notes
Contributor
|
Tick the box to add this pull request to the merge queue (same as
|
fix: set mr status to received when per_received is 100 even if per_o…
(cherry picked from commit 1492c9f) # Conflicts: # erpnext/controllers/sales_and_purchase_return.py
…der (#56667) Co-authored-by: Mihir Kandoi <kandoimihir@gmail.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
|
PR author is in the excluded authors list. |
…#56668) * fix: add permission checks in whitelisted functions (#53103) (cherry picked from commit a6e78c2) # Conflicts: # erpnext/stock/report/stock_qty_vs_batch_qty/stock_qty_vs_batch_qty.py * chore: resolve conflict --------- Co-authored-by: Priyal Rawal <135015851+Priyal208@users.noreply.github.com> Co-authored-by: Diptanil Saha <diptanil@frappe.io>
…-56662 fix: use correct variable to fetch valuation method (backport #56662)
(cherry picked from commit b9f330a)
(cherry picked from commit 17ef5d6)
…-56678 fix(gross_profit): correct GP calculation for rate adjustment debit notes (backport #56678)
Collaborator
Author
|
🎉 This PR is included in version 15.115.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated weekly release.