chore: declare bench frappe/erpnext dependencies - #16
Merged
Conversation
New modules need the app to declare which Frappe majors it supports. pyproject.toml had no [tool.bench.frappe-dependencies] section, so bench performed no compatibility check at install time and a mismatch would only surface at runtime. Range covers v15 and v16, matching how the app is developed and tested. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
erpnext belongs alongside frappe in [tool.bench.frappe-dependencies] — the app hard-requires it for the Project and Item doctypes, and bench checks each entry independently, so declaring only frappe left the ERPNext major unconstrained. CLAUDE.md claimed v15 in three places (Technology Stack ×2, Key Dependencies), which understated the supported range now that both majors are declared. Verified against the benches in use: frappe/erpnext 15.110.0 and 16.21.1. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
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.
pyproject.tomlhad no[tool.bench.frappe-dependencies]section at all, sobench get-app/bench install-appran no compatibility check — installing against an unsupported major would surface as a runtime failure rather than an install-time one. New modules need this declared.erpnextis declared alongsidefrappebecause the app hard-requires it for the Project and Item doctypes, and bench checks each entry independently — declaring onlyfrappewould have left the ERPNext major unconstrained.The range covers v15 and v16, matching the benches actually in use: frappe/erpnext
15.110.0and16.21.1.The commented-out
frappe~=15.0.0in[project].dependenciesis left as is — that is a pip dependency deliberately delegated to bench, and a separate mechanism from this section.CLAUDE.mdcorrectedIt claimed v15 in three places — Technology Stack (Framework, ERP) and Key Dependencies — which understated the supported range. All three now state
>=15.0.0,<17.0.0, with a note that the ranges live inpyproject.tomland the two should be kept in sync.Verification
{'frappe': '>=15.0.0,<17.0.0', 'erpnext': '>=15.0.0,<17.0.0'}🤖 Generated with Claude Code