Release policy
What you can rely on.
How often Kaleta is released, how sites update, and what never breaks without notice – for your own site and for the sites you build for clients. It applies from Kaleta 2.1.
A steady pace.
About one minor release a month with new features. Patch and security releases when they are needed. A major release at most once a year.
One-step updates.
The latest release is supported, and every earlier version reaches it in one step from Settings → Backups and updates. Each release is tested by updating older installations on MySQL and MariaDB.
Security on its own.
Security releases install themselves unless the administrator turns it off: the site backs up its database and checks the signature and the checksum first.
No surprise removals.
Before anything goes, it is announced, shown in System status on the sites that use it, kept for at least two minor releases and six months, and removed only in a major release.
A recorded contract.
The tools of the Claude connection, the design tokens and the builder elements are recorded in the repository. The tests fail if any of them is removed or changed.
A public record.
Every release is announced on GitHub and in the changelog here, in English, Czech and German.
ChangelogCompatibility
The public contract.
Covered by the rules above:
- The Claude connection (MCP) – tool names, parameters and their types, required parameters and each tool's annotations. The older Czech tool names keep working too.
- Design tokens – the stored names such as
--ka-barva-primarniand the English ones such as--ka-color-primary. - Builder elements and their content, so every saved page keeps rendering.
- The site export – it can be imported into the same or any later release.
- Addresses of your content – an update never changes them; when you change the address of a page, news item or category, Kaleta adds a redirect.
- The update channel and its signatures.
Not covered: PHP classes, functions and database tables (Kaleta has no plug-in API – build on the export, the Claude connection, webhooks and feeds), the HTML of the admin and the exact markup of public pages, and the wording of texts.
The full policy
The policy lives in the repository next to the code, and every change to it is public.