Skip to content

chore: sync develop into release/v1 (bench dependency declarations) - #17

Merged
Guru107 merged 4 commits into
release/v1from
develop
Jul 29, 2026
Merged

chore: sync develop into release/v1 (bench dependency declarations)#17
Guru107 merged 4 commits into
release/v1from
develop

Conversation

@Guru107

@Guru107 Guru107 commented Jul 29, 2026

Copy link
Copy Markdown
Owner

Brings release/v1 up to date with develop ahead of re-pointing the v1.2.1 tag.

What this carries

c9b9f5c declare [tool.bench.frappe-dependencies] with frappe = ">=15.0.0,<17.0.0"
5dfbfd3 add erpnext = ">=15.0.0,<17.0.0"; correct the v15-only claims in CLAUDE.md (Technology Stack ×2, Key Dependencies)
b559067, f4d9c98 merge commits from PRs #14 and #16

Before this, bench get-app / bench install-app ran no compatibility check at all, so an unsupported Frappe or ERPNext major would surface as a runtime failure rather than an install-time one.

Direction

release/v1 is currently one commit ahead of develop (8140577, the v1.2.1 republish, which the v1.2.1 tag points at). That commit stays where it is — this PR only moves content the other way, so the tag's current target is unaffected by the merge itself.

Verification

  • TOML parses; section resolves to {'frappe': '>=15.0.0,<17.0.0', 'erpnext': '>=15.0.0,<17.0.0'}
  • pre-commit run --all-files → exit 0, including check toml
  • No Python touched; full suite last run green at 72/72 on v15

🤖 Generated with Claude Code

Guru107 and others added 4 commits July 27, 2026 17:04
Merge pull request #13 from Guru107/develop
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>
chore: declare bench frappe/erpnext dependencies
@Guru107
Guru107 merged commit c2becd2 into release/v1 Jul 29, 2026
4 checks passed
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.

1 participant