Back to the changelog

v0.52.8

July 19, 2026

Stronger foundations: organization isolation in the busiest areas is now guaranteed "by construction" by the system itself, with an automatic guard preventing regressions; every sensitive page's permissions are under continuous test. Same app, much more robust underpinnings.

  • Security

    Organization isolation by construction

    In the busiest areas (items, tasks, flows, designer), your organization's boundary is now injected automatically by the system into every data access, instead of relying on dozens of manual checks scattered through the code: a forgotten check can no longer become a gap between organizations. An automatic pipeline guard prevents unprotected accesses from ever being reintroduced.

  • Security

    Page permissions under continuous test

    New automatic checks verify on every change that sensitive pages (users, management, administration) reject unauthorized roles: a permissions regression now stops the pipeline before it can reach production.

  • Integration

    Note for API integrators

    The `GET /events/raised` and `GET /flows/{id}/items` routes now return 400 with code `INVALID_PAGINATION` for invalid pagination parameters (previously the value was silently clamped). Anyone passing valid values will notice no difference.