This release includes 2 breaking changes for platform teams planning a safe upgrade.
✓ No known CVEs patched in this version
Topics
+2 more
Affected surfaces
ReleasePort's take
Light signalKoito v0.2.1 automates migration from PostgreSQL to local SQLite databases, triggered by KOITO_DATABASE_URL. Upgrades from v0.1.x must proceed through v0.2.1, and KOITO_SQLITE_ENABLED is no longer supported; backup before upgrading.
Why it matters: v0.1.x→v0.3.x upgrades require v0.2.1 as mandatory intermediate step. Automatic PostgreSQL-to-SQLite migration triggers on KOITO_DATABASE_URL; backup immediately before upgrade.
Summary
AI summaryBackup your data before upgrading as Koito will automatically migrate PostgreSQL to SQLite.
Changes in this release
| Type | Severity | Summary | CVE |
|---|---|---|---|
| Breaking | Medium |
Migrates data from PostgreSQL to local SQLite database Migrates data from PostgreSQL to local SQLite database Source: llm_adapter@2026-05-21 Confidence: low |
— |
| Breaking | Medium |
v0.1.x to v0.3.x upgrades must proceed through v0.2.1 first v0.1.x to v0.3.x upgrades must proceed through v0.2.1 first Source: llm_adapter@2026-05-21 Confidence: low |
— |
| Breaking | Medium |
KOITO_SQLITE_ENABLED environment variable no longer needed KOITO_SQLITE_ENABLED environment variable no longer needed Source: llm_adapter@2026-05-21 Confidence: low |
— |
| Feature | Medium |
Automatic migration triggered via KOITO_DATABASE_URL environment variable Automatic migration triggered via KOITO_DATABASE_URL environment variable Source: llm_adapter@2026-05-21 Confidence: high |
— |
Full changelog
IMPORTANT
This version exists as a bridge between the PostgreSQL v0.1.x and SQLite v0.3.x releases. It is highly recommended that you backup and/or export your data before upgrading to ensure you don't lose anything!. In my experience, the migration takes under a second and no data has been lost in my testing, but I will make no guarantees of this.
To trigger the automatic migration, you just need to ensure you have the KOITO_DATABASE_URL environment variable set. Then, Koito will automatically migrate all of your PostgreSQL data to a local SQLite database.
If you already migrated with KOITO_SQLITE_ENABLED=true in v0.1.8-10, this release is not important to you, as you are already on the new database. You can simply remove that variable after upgrading as it is no longer needed.
In the future, if you are upgrading from any v0.1.x version to any v0.3.x version, you will HAVE to upgrade to v0.2.1 to perform the migration first. So, it is highly recommended that you update to v0.2.1 sooner rather than later so that you can get some of the cool v0.3.0 changes that I have planned.
What's Changed
- chore: force sqlite migration by @gabehf in https://github.com/gabehf/Koito/pull/268
Full Changelog: https://github.com/gabehf/Koito/compare/v0.1.10...v0.2.1
Breaking Changes
- Database backend changes from PostgreSQL to SQLite; requires `KOITO_DATABASE_URL` for automatic migration
- `KOITO_SQLITE_ENABLED=true` flag is removed after migration
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About Koito
Koito is a modern, themeable scrobbler that you can use with any program that scrobbles to a custom ListenBrainz URL
Related context
Related tools
Earlier breaking changes
- v0.3.2 Migrate image cache system from old to new starting in v0.3.1; backup data folder first.
- v0.3.2 Migrate from PostgreSQL to SQLite required before any other updates for v0.1.x users.
- v0.3.1 Changes many API endpoints under /apis/web/v1/ and image URIs; client updates needed.
- v0.3.1 Migrates database from PostgreSQL to SQLite; backup required.
- v0.3.0 All PostgreSQL code and references have been removed; migration to SQLite required for v0.1.x users.
Beta — feedback welcome: [email protected]