Docs · Reference

Changelog

Caelo is still before 1.0 and releases often. Release notes for every version live on GitHub.

Where the release notes live

  • GitHub Releases: one release per version, with that version's notes, the signed release manifest and its Sigstore bundle. The newest release there is the current version.
  • CHANGELOG.md on the main branch: the same notes for all versions in one file, newest first, grouped into features, fixes and other changes.
  • In your admin under Settings, Caelo updates: the version you run and the notes of the release you can install next. See Updates and maintenance.

Every package, container image and the installer share one version number. The notes are generated from the commit messages of each release, so every entry names its commit and usually an issue number.

What pre-1.0 means here

  • The version number alone does not tell you how risky an update is. Before 1.0, minor and patch releases can change things, for example plugin and integration APIs, MCP tools or the command line. Read the release notes before you update.
  • The signed release information protects your site. Each release says whether it makes destructive database changes or changes your cloud setup. Those releases are never installed automatically, and the admin tells you what to do.
  • Automatic updates are optional. By default Caelo only tells you about a release. For a production site we recommend leaving it on "notify" or allowing only security fixes. Major releases never install automatically.
  • Errors instead of silent defaults. Until 1.0, code paths that could fall back to a default when data is missing fail with a structured error that names what is missing. That makes problems visible early, and it means you will see more error messages than in a mature product.
  • Releases are frequent. Upgrades are verified, backed up and roll back on failure. Still, keep your own backups.

Security releases

A release counts as a security fix only when its signed release information names a published GitHub Security Advisory. To report a vulnerability, use GitHub's private vulnerability reporting. More on the security page.

Something wrong or missing on this page? Open an issue on GitHub