One single change in this release:
Reversed course on new /api/app/status API call. It no longer causes a server restart on a tick age issue (i.e. broken timer). It now only logs a level 1 debug message, and safely returns an API response. Server restarts should only be handled by an external monitoring tool.
This tick age thing is an ongoing investigation into a very strange situation, seen after about 20 days of continuous running on Linux CentOS 7.2, Node v10.6.0 and AWS (S3) storage backend. Seemingly at random (but on multiple servers at the same time), all the Node.js timers and intervals seem to cease firing, but all other actions triggered by sockets or child processes keep running. The Cronicle daemon has to be restarted, sometimes SIGKILLed. CPU and memory are both fine.
I'm currently dumbfounded as to what could cause such a thing.