3 weeks ago 4 commits to master since this release
Some parts of the code were refactored. Nothing should change.
This release uses transactions with savepoints while older ones did use
them only without savepoints. The common database engines support this
so that this should not cause any problems.
4 weeks ago 12 commits to master since this release
This release contains 1 fix, 1 improvement and 1 cleanup
fix: multiple session duration limits for the same time window caused problems
if time for them was added
improvement: added a tolerance for the session duration limit session reset
vs extending so that a reset would happen a few seconds before the time was
cleanup: old serialization function which were never used were removed
1 month ago 15 commits to master since this release
New client versions will try to use this, but it does not cause any problems if the server does not support it (except some sync conflict warnings at the client)
1 month ago 16 commits to master since this release
This server version improves the support for a recent client feature
(manually adding used time) by making it an important change which
is synced without delay.
There are not any other changes.
2 months ago 22 commits to master since this release
This server version contains the support for the new features of the
client version 3.4.0 which will be released next week.
Moreover, there is the new environment variable ALWAYS_PRO which
allows unlocking the features of the premium version permanently.
Please note that client versions older than 3.4.0 will show that
the premium version will expire 1970 when enabling this, but this
does not cause any problems.
3 months ago 27 commits to master since this release
This release contains new features for TimeLimit 3.2.0 which will be released tomorrow. Without it, using the new features (deep category nesting and limit login categories) triggers a sync conflict and the changes will be rolled back.
Moreover, this updates the Node.JS version within the docker container and it fixes cache invalidation issues which occurred when assigning an App which was already part of another category.