v0.13.6
Enhancement
v0.13.6 - One owner per blueprint
A blueprint now belongs to exactly one collection, navigation or global, enforced by the database.
Changes
- A blueprint has exactly one owner. The seven shared owner rows in production were split into per-owner copies (for example
articleshared with thesecondcollection becamearticle_second) with entries, values and forms moved onto the copy, so nothing a template reads changed.