Every change documented, without hiding breaking updates behind marketing. Written for teams who maintain real projects over time.
The changelog exists to help developers, ops teams and project owners understand what changed, why it changed and whether action is required. It complements the documentation, it does not replace it.
Each release is tagged with a clear version number and grouped changes. Patch, minor and major updates are treated differently.
If an update can affect existing projects, it is marked clearly and explained. No silent changes to behaviour or data.
Changes are described per module where applicable, so you know exactly which part of the system is affected. See related modules when needed.
The changelog focuses on changes that matter in production, not internal refactors with no external impact.
UI changes, permission logic updates and workflow adjustments that affect how teams work in the admin panel.
Endpoint changes, authentication updates and behaviour differences in the API and integrations.
Fixes and improvements related to authentication, access control and protection mechanisms.
Each release follows a consistent structure so you can quickly scan or dive deeper when needed.
Track changes that affect templates, data access and integrations with external systems.
Understand deployment impact, upgrade safety and potential rollback considerations.
See how the platform evolves without digging through commit logs or internal notes.
The changelog shows what changed. The documentation explains how things work now.