Releases: muety/wakapi
Release 2.12.3
Release 2.12.2
Bug Fixes
Improvements
heartbeats table. In case your table is very large, the according migration will take a while (up to hours for very large instances). Thus, if you have more than several 100k records stored and you cannot afford a down time, it is recommended to manually run the SQL command mentioned here before performing the upgrade.
Release 2.12.1
Release 2.12.0
Features
Bug Fixes
Improvements
Structured Logging
In addition, we switched to using structured logging. As a result, all log messages produced by Wakapi now either have the following text format (dev mode)
time=2022-11-08T15:28:26.000-05:00 level=INFO msg=hello count=3
or are JSON objects (prod mode) like this:
{"time":"2022-11-08T15:28:26.000000000-05:00","level":"INFO","msg":"hello","count":3}
For some people, this might be a breaking change if they parse the current (now obsolete) log format for further processing such as monitoring or altering.
Also, Wakapi now bases on Go 1.23.
Release 2.11.2
Release 2.11.1
Bug Fixes
Release 2.11.0
Release 2.10.5
Bug Fixes
👉 Please note: due to the bug in #600, summaries were generated wrong since the last release. To get your coding data back on track again, please simply run the following SQL query in your database:
delete from summaries where from_time >= '2024-01-16';If you're the only user on your Wakapi instance, you can alternatively also log in, go to Settings -> Danger Zone and do Clear & regenerate summaries.
