Releases: muety/wakapi
Release 2.13.4
Release 2.13.3
Bug Fixes
Release 2.13.2
Bug Fixes
Major changes
There were some major timezone-related issues with Postgres (See #771). A workaround (not the final solution, though) was added in the context of #761. For Postgres users, this will likely result in their coding times to look different with this new version. Just so that you're prepared ...
Release 2.13.1
Release 2.13.0
Big new release featuring lots of changes 🚀!
New calculation logic
Most notably, we fundamentally changed the way how durations are calculated. In a nutshell, the updated logic – as requested by many users – is closer to that of WakaTime now and adopts WakaTime's notion of heartbeat timeouts.
Before this refactoring, Wakapi had a single timeout parameter that was responsible for two different things. On the one hand, it acted as a timeout in the actual sense of the word, i.e. controlled the maximum timespan between two heartbeats in order for them to still be considered as a contiguous piece of coding. On the other hand, we used this parameter for padding every "last" heartbeat in a sequence. With this release, we dropped padding entirely (WakaTime doesn't have such either) and instead allow for much larger timeouts (currently up to 1 hour). For details, please refer to #675. In fact, the default setting was increased from 2 minutes to 10 minutes (WakaTime uses 15 minutes).
- Default timeout: 10 minutes
- Minimum timeout: 1 minute
- Maximum timeout: 60 minutes
Custom, user-specific timeouts less than the minimum or greater than the maximum were truncated accordingly. Users who didn't have a custom timeout configured were migrated to the new default of 10 minutes. As a consequence, your coding time will most likely be different all of a sudden now, so in a very strict sense, you might even argue this is a breaking change.
The changes conducted as part of this refactoring also pave the way for implementing new features such as #101.
Please note
Big fundamental changes like this one often come along with unexpected errors and bugs. We expect such to be revealed over time, especially on custom, self-hosted instances with other databases (than MySQL, used by Wakapi.dev). Please bear with us and report any errors you encounter, so we can fix them soon 🐞.
TL;DR
Expect your coding time to vary after this new release (will probably be higher) ☝️.
In addition, this release features the following.
Features
- Calendar view (#338) - thanks to @justin-jiajia
- Change usernames (#739)
Bug Fixes
Improvements / other
Contributors
Assets 7
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.