ops/homelab

Fork 0

chore(deps): update gabehf/koito docker tag to v0.3.2 #23

Open

renovate-bot wants to merge 1 commit from renovate/gabehf-koito-0.x into main

renovate-bot commented

2026-07-08 01:10:35 +00:00

Member

This PR contains the following updates:

Package	Update	Change
gabehf/koito	minor	`v0.1.5` → `v0.3.2`

Release Notes

gabehf/Koito (gabehf/koito)

`v0.3.2`

Compare Source

⚠️ Caution: if you are upgrading from any version v0.1.x on PostgreSQL, you MUST upgrade to v0.2.1 to perform the SQLite migration before performing any other updates! If you are already on SQLite, you don't have to worry about this. ⚠️

⚠️ Versions v0.3.1 onwards contain a migration from the old image cache system to the new one, which has worked in testing but I make no guarantees you won't lose your uploaded images. Make sure you backup your data folder before updating from a version before v0.3.1! ⚠️

What's Changed

chore: fix typo in all its instances by @paezdavid in #290
fix: add timezone to stats cache key by @gabehf in #289
fix: adjust query for deezer images by @gabehf in #288
fix: delete listens path in client by @gabehf in #293
fix: load background color before rendering by @gabehf in #294

New Contributors

@paezdavid made their first contribution in #290

Full Changelog: https://github.com/gabehf/Koito/compare/v0.3.1...v0.3.2

`v0.3.1`

Compare Source

⚠️ This update contains a migration from the old image cache system to the new one, which has worked in testing but I make no guarantees you won't lose your uploaded images. Make sure you backup your data folder before updating! ⚠️

Highlights

Refreshed UI

The UI has a new look! I think it does a good job of not being so boring but still providing a lot of quick stats for your listening data.

API Changes

Many API endpoints under the /apis/web/v1/ routes, as well as the image URIs, have changed. If you were previously using one of these endpoints for your own purposes, you will likely need to fix the endpoint. You can look at the engine/routes.go file to see a list of all the endpoints. These changes are in preparation for eventual API documentation once I deem the API stable.

What's Changed

chore: rewrite api surface by @gabehf in #265
Fix/change listen track model by @gabehf in #273
feat: A very big PR that redesigns the UI among other things by @gabehf in #275
fix: add head middleware by @gabehf in #277
chore: tests for conflicting listens on merge by @gabehf in #279
UI/tweaks by @gabehf in #280
feat: streaks and more stats by @gabehf in #282
chore: add cache to stats handler by @gabehf in #281
fix: nil mbz client passed to maloja importer by @gabehf in #283
chore: remove all postgres code and references by @gabehf in #278

Full Changelog: https://github.com/gabehf/Koito/compare/v0.2.1...v0.3.1

`v0.3.0`

Compare Source

Update to v0.3.1 instead.

`v0.2.1`

Compare Source

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.

Then, make sure you remove the KOITO_DATABASE_URL variable from your configuration, otherwise Koito will fail to start if it restarts again as it will try and fail to perform another migration.

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 #268

Full Changelog: https://github.com/gabehf/Koito/compare/v0.1.10...v0.2.1

`v0.2.0`

Compare Source

Update to v0.2.1 instead.

Full Changelog: https://github.com/gabehf/Koito/compare/v0.1.10...v0.2.0

`v0.1.10`

Compare Source

What's Changed

feat: purge all data endpoint by @gabehf in #261
fix: boolean logic error on allowed hosts check by @gabehf in #264
feat: version checker and notification dot by @gabehf in #266
fix: run psql migrations before migrating to sqlite by @gabehf in #267

Full Changelog: https://github.com/gabehf/Koito/compare/v0.1.9...v0.1.10

`v0.1.9`

Compare Source

What's Changed

fix: add and remove artists from track in sqlite by @gabehf in #260

Full Changelog: https://github.com/gabehf/Koito/compare/v0.1.8...v0.1.9

`v0.1.8`

Compare Source

Highlights

SQLite support!

Before migrating, be sure to create an export of your data to ensure you do not lose any listening history! However, migration is a read-only process for your PostgreSQL database, so no data loss should occur (but I won't guarantee it for liability's sake). To migrate automatically, simply add KOITO_SQLITE_ENABLED=true to your environment variables. When Koito sees both that and KOITO_DATABASE_URL populated, it will automatically create a koito.db in your configuration root that will have all of your listening data, and Koito will immediately start using the new SQLite database.

Migration to SQLite will happen automatically on v0.2.0, so it is highly recommended to migrate manually beforehand to make sure everything goes smoothly!

Note that if Koito restarts and sees both environment variables populated, it will attempt another migration and fail to start, so after migrating you should remove KOITO_DATABASE_URL once you verify all your listening history is intact.

KOITO_ALLOWED_HOSTS is dead!

Remove it from your configuration. You don't need it, and it's value is now ignored and all hosts are allowed. I added this in the case Koito got more complicated, and I wanted to avoid a gethomepage-type situation where it gets added later on and causes issues with existing deployments. However, I've decided its too much trouble than it's worth, and I don't think Koito will grow enough in complexity to warrant it as an important security measure. This will also mean that, once SQLite is enabled by default in v0.2.0, Koito will be able to start with one container and absolutely zero configuration needed. A big win for simplicity!

Edit artists in the UI

Thank you to @onespaceman for the update that allows for adding and removing artists from tracks and albums in the UI.

What's Changed

chore: refactor db interface into stores by @gabehf in #245
feat: sqlite support by @gabehf in #248
fix: improve ui when there is no data by @gabehf in #249
Fix artist name parsing for Last.fm imports by @megatwig in #207
Fix artist images: filter Last.fm placeholder, reorder providers by @safierinx-a in #233
Fix: suppress spurious error log when Authorization header is absent by @joffrey-b in #243
Added clickable artist on album and track pages by @joffrey-b in #246
fix: nil pointer panic by @mikkelrask in #237
fix: don't treat tracks with similar title as the same track by @jostyee in #247
chore: remove allowed hosts configuration by @gabehf in #250
fix: only show primary artist on album page by @gabehf in #251
fix: add a permissions check for config dir by @gabehf in #252
fix: unique mbid by @gabehf in #253
feat: reset password by @gabehf in #254
feat: add client to koito export and import by @gabehf in #255
fix: migration fixes by @gabehf in #257
Feat: Edit Artists by @onespaceman in #199

New Contributors

@megatwig made their first contribution in #207
@safierinx-a made their first contribution in #233
@joffrey-b made their first contribution in #243
@mikkelrask made their first contribution in #237
@jostyee made their first contribution in #247

Full Changelog: https://github.com/gabehf/Koito/compare/v0.1.7...v0.1.8

`v0.1.7`

Compare Source

What's Changed

fix: add null check for top charts bg gradient by @gabehf in #193
ui: tweaks and fixes by @gabehf in #194

Full Changelog: https://github.com/gabehf/Koito/compare/0.1.6...v0.1.7

`v0.1.6`

Compare Source

What's Changed

fix: ensure mbids in mbidmapping are discovered when importing from listenbrainz by @gabehf in #180
fix: gradient background on top charts by @gabehf in #181
docs: fix typo in index.mdx by @PythonGermany in #182
feat: add api key auth to web api by @gabehf in #183
fix: invalid json response when login gate is disabled by @gabehf in #184
fix: rewind navigation by @gabehf in #191

New Contributors

@PythonGermany made their first contribution in #182

Full Changelog: https://github.com/gabehf/Koito/compare/v0.1.5...0.1.6

Configuration

📅 Schedule: (UTC)

Branch creation
- At any time (no schedule defined)
Automerge
- At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [gabehf/koito](https://github.com/gabehf/Koito) | minor | `v0.1.5` → `v0.3.2` | --- ### Release Notes <details> <summary>gabehf/Koito (gabehf/koito)</summary> ### [`v0.3.2`](https://github.com/gabehf/Koito/releases/tag/v0.3.2) [Compare Source](https://github.com/gabehf/Koito/compare/v0.3.1...v0.3.2) **⚠️ Caution: if you are upgrading from any version v0.1.x on PostgreSQL, you MUST upgrade to v0.2.1 to perform the SQLite migration before performing any other updates! If you are already on SQLite, you don't have to worry about this. ⚠️** **⚠️ Versions v0.3.1 onwards contain a migration from the old image cache system to the new one, which has worked in testing but I make no guarantees you won't lose your uploaded images. Make sure you backup your data folder before updating from a version before v0.3.1! ⚠️** #### What's Changed - chore: fix typo in all its instances by [@paezdavid](https://github.com/paezdavid) in [#290](https://github.com/gabehf/Koito/pull/290) - fix: add timezone to stats cache key by [@gabehf](https://github.com/gabehf) in [#289](https://github.com/gabehf/Koito/pull/289) - fix: adjust query for deezer images by [@gabehf](https://github.com/gabehf) in [#288](https://github.com/gabehf/Koito/pull/288) - fix: delete listens path in client by [@gabehf](https://github.com/gabehf) in [#293](https://github.com/gabehf/Koito/pull/293) - fix: load background color before rendering by [@gabehf](https://github.com/gabehf) in [#294](https://github.com/gabehf/Koito/pull/294) #### New Contributors - [@paezdavid](https://github.com/paezdavid) made their first contribution in [#290](https://github.com/gabehf/Koito/pull/290) **Full Changelog**: <https://github.com/gabehf/Koito/compare/v0.3.1...v0.3.2> ### [`v0.3.1`](https://github.com/gabehf/Koito/releases/tag/v0.3.1) [Compare Source](https://github.com/gabehf/Koito/compare/v0.3.0...v0.3.1) **⚠️ Caution: if you are upgrading from any version v0.1.x on PostgreSQL, you MUST upgrade to v0.2.1 to perform the SQLite migration before performing any other updates! If you are already on SQLite, you don't have to worry about this. ⚠️** **⚠️ This update contains a migration from the old image cache system to the new one, which has worked in testing but I make no guarantees you won't lose your uploaded images. Make sure you backup your data folder before updating! ⚠️** #### Highlights ##### Refreshed UI The UI has a new look! I think it does a good job of not being so boring but still providing a lot of quick stats for your listening data. ##### API Changes Many API endpoints under the `/apis/web/v1/` routes, as well as the image URIs, have changed. If you were previously using one of these endpoints for your own purposes, you will likely need to fix the endpoint. You can look at the `engine/routes.go` file to see a list of all the endpoints. These changes are in preparation for eventual API documentation once I deem the API stable. #### What's Changed - chore: rewrite api surface by [@gabehf](https://github.com/gabehf) in [#265](https://github.com/gabehf/Koito/pull/265) - Fix/change listen track model by [@gabehf](https://github.com/gabehf) in [#273](https://github.com/gabehf/Koito/pull/273) - feat: A very big PR that redesigns the UI among other things by [@gabehf](https://github.com/gabehf) in [#275](https://github.com/gabehf/Koito/pull/275) - fix: add head middleware by [@gabehf](https://github.com/gabehf) in [#277](https://github.com/gabehf/Koito/pull/277) - chore: tests for conflicting listens on merge by [@gabehf](https://github.com/gabehf) in [#279](https://github.com/gabehf/Koito/pull/279) - UI/tweaks by [@gabehf](https://github.com/gabehf) in [#280](https://github.com/gabehf/Koito/pull/280) - feat: streaks and more stats by [@gabehf](https://github.com/gabehf) in [#282](https://github.com/gabehf/Koito/pull/282) - chore: add cache to stats handler by [@gabehf](https://github.com/gabehf) in [#281](https://github.com/gabehf/Koito/pull/281) - fix: nil mbz client passed to maloja importer by [@gabehf](https://github.com/gabehf) in [#283](https://github.com/gabehf/Koito/pull/283) - chore: remove all postgres code and references by [@gabehf](https://github.com/gabehf) in [#278](https://github.com/gabehf/Koito/pull/278) **Full Changelog**: <https://github.com/gabehf/Koito/compare/v0.2.1...v0.3.1> ### [`v0.3.0`](https://github.com/gabehf/Koito/releases/tag/v0.3.0) [Compare Source](https://github.com/gabehf/Koito/compare/v0.2.1...v0.3.0) Update to v0.3.1 instead. ### [`v0.2.1`](https://github.com/gabehf/Koito/releases/tag/v0.2.1) [Compare Source](https://github.com/gabehf/Koito/compare/v0.2.0...v0.2.1) ### 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. Then, make sure you remove the `KOITO_DATABASE_URL` variable from your configuration, otherwise Koito will fail to start if it restarts again as it will try and fail to perform another migration. 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](https://github.com/gabehf) in [#268](https://github.com/gabehf/Koito/pull/268) **Full Changelog**: <https://github.com/gabehf/Koito/compare/v0.1.10...v0.2.1> ### [`v0.2.0`](https://github.com/gabehf/Koito/releases/tag/v0.2.0) [Compare Source](https://github.com/gabehf/Koito/compare/v0.1.10...v0.2.0) Update to v0.2.1 instead. **Full Changelog**: <https://github.com/gabehf/Koito/compare/v0.1.10...v0.2.0> ### [`v0.1.10`](https://github.com/gabehf/Koito/releases/tag/v0.1.10) [Compare Source](https://github.com/gabehf/Koito/compare/v0.1.9...v0.1.10) #### What's Changed - feat: purge all data endpoint by [@gabehf](https://github.com/gabehf) in [#261](https://github.com/gabehf/Koito/pull/261) - fix: boolean logic error on allowed hosts check by [@gabehf](https://github.com/gabehf) in [#264](https://github.com/gabehf/Koito/pull/264) - feat: version checker and notification dot by [@gabehf](https://github.com/gabehf) in [#266](https://github.com/gabehf/Koito/pull/266) - fix: run psql migrations before migrating to sqlite by [@gabehf](https://github.com/gabehf) in [#267](https://github.com/gabehf/Koito/pull/267) **Full Changelog**: <https://github.com/gabehf/Koito/compare/v0.1.9...v0.1.10> ### [`v0.1.9`](https://github.com/gabehf/Koito/releases/tag/v0.1.9) [Compare Source](https://github.com/gabehf/Koito/compare/v0.1.8...v0.1.9) #### What's Changed - fix: add and remove artists from track in sqlite by [@gabehf](https://github.com/gabehf) in [#260](https://github.com/gabehf/Koito/pull/260) **Full Changelog**: <https://github.com/gabehf/Koito/compare/v0.1.8...v0.1.9> ### [`v0.1.8`](https://github.com/gabehf/Koito/releases/tag/v0.1.8) [Compare Source](https://github.com/gabehf/Koito/compare/v0.1.7...v0.1.8) #### Highlights ##### SQLite support! **Before migrating, be sure to create an export of your data to ensure you do not lose any listening history!** However, migration is a read-only process for your PostgreSQL database, so no data loss *should* occur (but I won't guarantee it for liability's sake). To migrate automatically, simply add `KOITO_SQLITE_ENABLED=true` to your environment variables. When Koito sees both that and `KOITO_DATABASE_URL` populated, it will automatically create a `koito.db` in your configuration root that will have all of your listening data, and Koito will immediately start using the new SQLite database. **Migration to SQLite will happen automatically on v0.2.0**, so it is **highly recommended to migrate manually** beforehand to make sure everything goes smoothly! Note that if Koito restarts and sees both environment variables populated, it will attempt another migration and fail to start, so after migrating you should remove `KOITO_DATABASE_URL` once you verify all your listening history is intact. ##### KOITO\_ALLOWED\_HOSTS is dead! Remove it from your configuration. You don't need it, and it's value is now ignored and all hosts are allowed. I added this in the case Koito got more complicated, and I wanted to avoid a gethomepage-type situation where it gets added later on and causes issues with existing deployments. However, I've decided its too much trouble than it's worth, and I don't think Koito will grow enough in complexity to warrant it as an important security measure. This will also mean that, once SQLite is enabled by default in v0.2.0, Koito will be able to start with one container and absolutely **zero** configuration needed. A big win for simplicity! ##### Edit artists in the UI Thank you to [@onespaceman](https://github.com/onespaceman) for the update that allows for adding and removing artists from tracks and albums in the UI. #### What's Changed - chore: refactor db interface into stores by [@gabehf](https://github.com/gabehf) in [#245](https://github.com/gabehf/Koito/pull/245) - feat: sqlite support by [@gabehf](https://github.com/gabehf) in [#248](https://github.com/gabehf/Koito/pull/248) - fix: improve ui when there is no data by [@gabehf](https://github.com/gabehf) in [#249](https://github.com/gabehf/Koito/pull/249) - Fix artist name parsing for Last.fm imports by [@megatwig](https://github.com/megatwig) in [#207](https://github.com/gabehf/Koito/pull/207) - Fix artist images: filter Last.fm placeholder, reorder providers by [@safierinx-a](https://github.com/safierinx-a) in [#233](https://github.com/gabehf/Koito/pull/233) - Fix: suppress spurious error log when Authorization header is absent by [@joffrey-b](https://github.com/joffrey-b) in [#243](https://github.com/gabehf/Koito/pull/243) - Added clickable artist on album and track pages by [@joffrey-b](https://github.com/joffrey-b) in [#246](https://github.com/gabehf/Koito/pull/246) - fix: nil pointer panic by [@mikkelrask](https://github.com/mikkelrask) in [#237](https://github.com/gabehf/Koito/pull/237) - fix: don't treat tracks with similar title as the same track by [@jostyee](https://github.com/jostyee) in [#247](https://github.com/gabehf/Koito/pull/247) - chore: remove allowed hosts configuration by [@gabehf](https://github.com/gabehf) in [#250](https://github.com/gabehf/Koito/pull/250) - fix: only show primary artist on album page by [@gabehf](https://github.com/gabehf) in [#251](https://github.com/gabehf/Koito/pull/251) - fix: add a permissions check for config dir by [@gabehf](https://github.com/gabehf) in [#252](https://github.com/gabehf/Koito/pull/252) - fix: unique mbid by [@gabehf](https://github.com/gabehf) in [#253](https://github.com/gabehf/Koito/pull/253) - feat: reset password by [@gabehf](https://github.com/gabehf) in [#254](https://github.com/gabehf/Koito/pull/254) - feat: add client to koito export and import by [@gabehf](https://github.com/gabehf) in [#255](https://github.com/gabehf/Koito/pull/255) - fix: migration fixes by [@gabehf](https://github.com/gabehf) in [#257](https://github.com/gabehf/Koito/pull/257) - Feat: Edit Artists by [@onespaceman](https://github.com/onespaceman) in [#199](https://github.com/gabehf/Koito/pull/199) #### New Contributors - [@megatwig](https://github.com/megatwig) made their first contribution in [#207](https://github.com/gabehf/Koito/pull/207) - [@safierinx-a](https://github.com/safierinx-a) made their first contribution in [#233](https://github.com/gabehf/Koito/pull/233) - [@joffrey-b](https://github.com/joffrey-b) made their first contribution in [#243](https://github.com/gabehf/Koito/pull/243) - [@mikkelrask](https://github.com/mikkelrask) made their first contribution in [#237](https://github.com/gabehf/Koito/pull/237) - [@jostyee](https://github.com/jostyee) made their first contribution in [#247](https://github.com/gabehf/Koito/pull/247) **Full Changelog**: <https://github.com/gabehf/Koito/compare/v0.1.7...v0.1.8> ### [`v0.1.7`](https://github.com/gabehf/Koito/releases/tag/v0.1.7) [Compare Source](https://github.com/gabehf/Koito/compare/0.1.6...v0.1.7) #### What's Changed - fix: add null check for top charts bg gradient by [@gabehf](https://github.com/gabehf) in [#193](https://github.com/gabehf/Koito/pull/193) - ui: tweaks and fixes by [@gabehf](https://github.com/gabehf) in [#194](https://github.com/gabehf/Koito/pull/194) **Full Changelog**: <https://github.com/gabehf/Koito/compare/0.1.6...v0.1.7> ### [`v0.1.6`](https://github.com/gabehf/Koito/releases/tag/v0.1.6) [Compare Source](https://github.com/gabehf/Koito/compare/v0.1.5...0.1.6) #### What's Changed - fix: ensure mbids in mbidmapping are discovered when importing from listenbrainz by [@gabehf](https://github.com/gabehf) in [#180](https://github.com/gabehf/Koito/pull/180) - fix: gradient background on top charts by [@gabehf](https://github.com/gabehf) in [#181](https://github.com/gabehf/Koito/pull/181) - docs: fix typo in index.mdx by [@PythonGermany](https://github.com/PythonGermany) in [#182](https://github.com/gabehf/Koito/pull/182) - feat: add api key auth to web api by [@gabehf](https://github.com/gabehf) in [#183](https://github.com/gabehf/Koito/pull/183) - fix: invalid json response when login gate is disabled by [@gabehf](https://github.com/gabehf) in [#184](https://github.com/gabehf/Koito/pull/184) - fix: rewind navigation by [@gabehf](https://github.com/gabehf) in [#191](https://github.com/gabehf/Koito/pull/191) #### New Contributors - [@PythonGermany](https://github.com/PythonGermany) made their first contribution in [#182](https://github.com/gabehf/Koito/pull/182) **Full Changelog**: <https://github.com/gabehf/Koito/compare/v0.1.5...0.1.6> </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate).

renovate-bot added 1 commit

2026-07-08 01:10:35 +00:00

Update gabehf/koito Docker tag to v0.3.2 bb28d1a408

renovate-bot changed title from ~~Update gabehf/koito Docker tag to v0.3.2~~ to chore(deps): update gabehf/koito docker tag to v0.3.2

2026-07-17 23:10:26 +00:00

renovate-bot changed title from ~~chore(deps): update gabehf/koito docker tag to v0.3.2~~ to Update gabehf/koito Docker tag to v0.3.2

2026-07-21 01:07:47 +00:00

renovate-bot changed title from ~~Update gabehf/koito Docker tag to v0.3.2~~ to chore(deps): update gabehf/koito docker tag to v0.3.2

2026-07-21 02:07:54 +00:00