Frappe Framework
Full-stack low-code web framework built with Python and JavaScript
Two trains ship the same features minutes apart while v16 absorbs the CRM stack.
◆Recent moves
- 7d ago
v15 gains a between filter and a richer activity timeline
The v15 half of a same-minute pair with v16.31.0: a between filter for numbers, dates, and date-times, and an activity timeline that now logs edits, milestones, and shares with per-field permission checks. Backporting both to the LTS line shows which features Frappe considers portable.
View source ↗ - 7d ago
Between filter and activity milestones land on v16 too
The v16 twin of v15.118.0, carrying the identical between filter and activity timeline work under different PR numbers. The only divergence is in the fixes, where v16 handles duplicate Desktop Icon entries that were breaking app installation.
View source ↗ - 14d ago
Autocomplete searches descriptions; CRM internals move in
Autocomplete dropdowns start searching option descriptions, and the shared CRM and Helpdesk feature set moves into v16. The rest is permission tightening — Report scripts limited to approved methods, link fields hiding titles from users who cannot view the record, Custom Field rename restricted to POST.
View source ↗ - 14d ago
Recorder adds a document lifecycle timeline
Recorder gains a document lifecycle timeline showing how long each step takes and which apps are involved, behind an administrator toggle. For a framework where a single save fans out across apps, per-step attribution is the piece that makes performance work possible.
View source ↗ - 20d ago
Report exports switch to linked-record titles
A breaking change on the LTS line: report exports now show linked-record titles rather than internal names, so files match what the report displays. Child-table lookups also switch to checking the parent document's access rights, resolving spurious permission warnings.
View source ↗ - 20d ago
Cloud Settings in Desk; linked-account sign-in hardened
The v16 side of the export change, plus Cloud Settings in Desk for Frappe Cloud v2 single-site setups. Sign-in gets the more consequential work: linked-account logins move to one-time codes with reuse and expiry rejected, and Google sign-in details stay on the server instead of passing through the browser.
View source ↗