-
Notifications
You must be signed in to change notification settings - Fork 7.4k
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
fix: Quality Inspection Parameter migration - DuplicateEntryError due to case sensitivity (backport #37499) #37916
Merged
s-aga-r
merged 1 commit into
version-14-hotfix
from
mergify/bp/version-14-hotfix/pr-37499
Nov 5, 2023
Merged
fix: Quality Inspection Parameter migration - DuplicateEntryError due to case sensitivity (backport #37499) #37916
s-aga-r
merged 1 commit into
version-14-hotfix
from
mergify/bp/version-14-hotfix/pr-37499
Nov 5, 2023
Conversation
This file contains 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
@Mergifyio backport version-14 |
✅ Backports have been created
|
mergify bot
added a commit
that referenced
this pull request
Nov 5, 2023
… to case sensitivity (backport #37499) (#37916) fix: Quality Inspection Parameter migration - DuplicateEntryError due to case sensitivity (#37499) * fix: account for case-insensitive database primary key for parameter names * chore: linting (cherry picked from commit b099590) Co-authored-by: Richard Case <[email protected]> (cherry picked from commit eb3630b)
s-aga-r
pushed a commit
that referenced
this pull request
Nov 5, 2023
… to case sensitivity (backport #37499) (backport #37916) (#37919) fix: Quality Inspection Parameter migration - DuplicateEntryError due to case sensitivity (backport #37499) (#37916) fix: Quality Inspection Parameter migration - DuplicateEntryError due to case sensitivity (#37499) * fix: account for case-insensitive database primary key for parameter names * chore: linting (cherry picked from commit b099590) Co-authored-by: Richard Case <[email protected]> (cherry picked from commit eb3630b) Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
frappe-pr-bot
pushed a commit
that referenced
this pull request
Nov 8, 2023
# [14.47.0](v14.46.7...v14.47.0) (2023-11-08) ### Bug Fixes * `TypeError` in PR for non-stock item ([ef4471f](ef4471f)) * add missing disbursement account in update_old_loans patch ([ad64065](ad64065)) * add translation wrapper (backport [#37911](#37911)) ([#37946](#37946)) ([c53d281](c53d281)) * don't reset rate if greater than zero in standalone debit note (backport [#37935](#37935)) ([#37940](#37940)) ([64658fc](64658fc)) * fetch asset received but not billed account only when needed ([7df4009](7df4009)) * gov compliance for tax withholding report ([#37590](#37590)) ([273cc35](273cc35)) * In-Transit Warehouse company filter (backport [#37796](#37796)) ([#37797](#37797)) ([0b1da08](0b1da08)) * link between parent and child procedure (backport [#37903](#37903)) ([#37943](#37943)) ([24da29a](24da29a)) * list index out of range ([#37880](#37880)) ([05fed9e](05fed9e)) * make `Material Request Item` required if `Material Request` is set in PO (backport [#37928](#37928)) ([#37936](#37936)) ([c870120](c870120)) * permission error while creating Supplier Quotation from Portal (backport [#37864](#37864)) ([#37870](#37870)) ([1a3dae0](1a3dae0)) * **plaid:** Do not sync pending transactions ([ffdc11b](ffdc11b)) * POS change amount gl entry with no amount ([#37799](#37799)) ([5e1a89b](5e1a89b)) * Quality Inspection Parameter migration - DuplicateEntryError due to case sensitivity (backport [#37499](#37499)) ([#37916](#37916)) ([eb3630b](eb3630b)) * remove voucher type and no for Item and Warehouse based reposting (backport [#37849](#37849)) ([#37850](#37850)) ([e19cade](e19cade)) * standard submit perm in repost ledger for editable invoices (backport [#37826](#37826)) ([#37854](#37854)) ([69b569d](69b569d)) * status for over delivery or billing ([d8e7430](d8e7430)) * type error on new payment entry ([38184f7](38184f7)) * typo in AR report ([3d72ec7](3d72ec7)) * validate so item with qtn ([4a225b0](4a225b0)) ### Features * reserved production plan sub assembly items (backport [#37884](#37884)) ([#37926](#37926)) ([4de97a4](4de97a4)) * settings page for repost ([09cde5d](09cde5d)) * **Stock Balance:** add filters from route (backport [#37836](#37836)) ([#37839](#37839)) ([e8a706a](e8a706a)) ### Performance Improvements * Add index to supplier invoice field (backport [#37861](#37861)) ([#37862](#37862)) ([2c93f81](2c93f81)) * index return against for purchase invoice (backport [#37881](#37881)) ([#37882](#37882)) ([fed25fa](fed25fa))
🎉 This PR is included in version 14.47.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This is an automatic backport of pull request #37499 done by Mergify.
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refresh
will re-evaluate the rules@Mergifyio rebase
will rebase this PR on its base branch@Mergifyio update
will merge the base branch into this PR@Mergifyio backport <destination>
will backport this PR on<destination>
branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.com