Skip to content

Kaeso 0.2.2. Released 18 October 2026, with 10 changes.

Released
Changes
10 changes
In this release
Added, Changed and Fixed
The release on GitHub (opens in a new tab)

Kaeso 0.2.2 lets installs update themselves in a daily or weekly window, and it replaces the updates.apply setting with updates.mode, so remove apply from any TOML file before you upgrade. Installs now look for releases at Kaeso's own update service instead of GitHub's API, so they need outgoing access to it or a mirror set in updates.releases_url. Each install has one time zone that the console uses for every time it shows, and users see a What's new dialog once after an update. The release also splits the instance settings into General, Logging and System pages and fixes phone zoom and the sign-in method prompt.

  • Breaking: updates.apply and KAESO_UPDATES_APPLY are replaced by updates.mode and KAESO_UPDATES_MODE; remove apply from any TOML file before you upgrade. (#160 (opens in a new tab))

Contributors: @dvnold

Full changes: v0.2.1...v0.2.2 (opens in a new tab)

Added

  • Each install has one IANA time zone, set in instance.timezone (KAESO_INSTANCE_TIMEZONE, default UTC). The setup page takes the first user's browser zone, instance admins change it under General, and the console shows every time in it. Platform API responses carry it in the Kaeso-Time-Zone header, and API timestamps stay RFC 3339 in UTC. (#159 (opens in a new tab))
  • Updates install either manually or automatically, in a daily or weekly window in the install's time zone, set with updates.mode (KAESO_UPDATES_MODE, manual or automatic). Major releases and releases with manual steps always wait for an admin, and only updates.check turns off looking for releases. updates.apply is replaced by updates.mode, and a TOML configuration that still sets apply is refused at start. (#160 (opens in a new tab))
  • After an update, the console shows what changed once, in a What's new dialog with the release's artwork and an option to show its notes. It lists each release since the last version the user saw, up to 10, newest first, and records the version as seen when the dialog closes. The Platform API adds GET /me/whats-new and POST /me/whats-new/seen for this. (#161 (opens in a new tab))
  • Each release gets its own artwork, chosen once by Kaeso's update service and stored with the release, so installs keep the same picture for a version. The What's new dialog draws the stored artwork and falls back to the version's own artwork when a spec is missing or unreadable. The UI library's ReleaseArt draws eight geometric styles in twelve palettes from a spec. (#169 (opens in a new tab))

UI library

  • The UI library adds ReleaseArt for abstract release artwork and releaseArtSvg for writing the same picture as a standalone SVG file. StatusDot takes an optional icon, and setFormatTimeZone makes formatDate, formatRelative and chart axes show times in one IANA zone, while calendar pickers keep local days. (#157 (opens in a new tab))

Changed

  • Instance settings are split into General, Logging and System pages, with General first in the sidebar. The System page holds the email transport and a Send test email button, and the old /settings/instance/settings address is removed without a redirect. (#158 (opens in a new tab))
  • Installs look for new releases at Kaeso's own update service instead of GitHub's API, and updates.releases_url now defaults to it. A mirror that answers in the same format or in GitHub's releases format still works, and installs need outgoing access to the service. (#162 (opens in a new tab))

Console

  • The What's new dialog only moves forward now, with Next through missed releases and Continue on the last one, so the Back button is gone. (#168 (opens in a new tab))

Fixed

  • Phones no longer zoom in when a text field is tapped in the console, the documentation or the showcase. Text fields render at 16px on touch screens, quick second taps on buttons no longer zoom, and pinch zoom still works. (#154 (opens in a new tab))
  • The recent sign-in dialog waits for the profile and asks the gateway which methods apply to the account, then offers exactly one way first. People without a password, such as single sign-on accounts, no longer see a password field, and disabled methods are not offered. (#156 (opens in a new tab))

More releases