Changelog
User-visible changes to Ertas, the catalogue, the docs, and the export pipeline.
This page records user-visible changes to Ertas, the model catalogue, the docs, and the export pipeline. Internal infrastructure changes that do not affect what users can do are omitted; if it does not change behaviour you would notice, it does not belong here.
Entries are dated and grouped by month. The most recent month is at the top.
What is recorded here
The categories that earn an entry:
| Category | What it covers |
|---|---|
| Catalogue | New base models added or removed; license changes; deprecations |
| Studio | Feature additions, UI changes, default-value changes, plan structure changes |
| Export | Changes to the GGUF bundle contents, the Modelfile, the install scripts |
| Docs | New sections, page reorganisations, factual corrections that change a recommended workflow |
| Pricing | Changes to plan grants, credit pricing, or storage quotas |
| Breaking | Anything that would break an existing user's running script or saved config |
Entries that are pure bug fixes ("loss curve display flickered on Safari") are not in the changelog; treat the absence of an entry as a non-event rather than a confirmation that nothing changed.
2026-05
Docs. First full version of the public docs published, covering Get Started, Datasets, Studio, Export, Ship, Cookbook, and Reference.
Export. GGUF bundle gains install.bat for Windows alongside the existing install.sh; both scripts now derive the Ollama model name from the bundle folder with regex sanitisation.
Catalogue. Gemma 4 E2B added (5.1B total parameters, A10G-only). Qwen 2.5 Coder family (1.5B, 3B, 7B) added.
Studio. Dataset import from Hugging Face now requires a rights-attestation checkbox before the dataset can be saved.
Subscribe-by-checking
There is no email subscription for the changelog today. The recommended pattern is to bookmark this page and check it on the cadence that matches how much your work depends on Ertas's behaviour: weekly if you are actively building, monthly if you have a model in production and want to know about catalogue or export changes.
When breaking changes ship, the entry in this changelog will be tagged with Breaking and the relevant docs pages will gain a Callout pointing to the changelog entry. If you read the docs without checking the changelog and a Callout surprises you, the Callout is doing its job.
A note on retroactive entries
Ertas shipped many things before this changelog existed. Rather than fabricate a long backfill, the rule is: anything that shipped before 2026-05 is implicitly part of the initial public release, and the docs themselves are the source of truth for what behaviour is current. If you find a behaviour that contradicts what the docs say, file it as a docs bug; the canonical answer is what the code does today, and the changelog is the diary going forward.