You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our monitoring system complained about our Matomo not being up to date. Though we did update as soon as the Docker image was released, the monitoring system kept throwing alerts. Why was that?
The CHANGELOG.md is not the changelog of the Matomo application, but a changelog for developers depending on Matomo. As nothing changed with 3.7.0., there is no entry.
Our monitoring system complained about our Matomo not being up to date. Though we did update as soon as the Docker image was released, the monitoring system kept throwing alerts. Why was that?
Because in v3.7.0
CHANGELOG.md
has not been updated, and thus the monitoring tool thought, this was still v3.6.1. Let's not discuss whether that is a good metric, but focus on why this is not done automatically somehow. On the tag to v3.8.0-b4 the version number inCHANGELOG.md
switched all the way from 3.6.1 to 3.8.0 even though whe are obviously not there yet.Can you guys please fix this?
The text was updated successfully, but these errors were encountered: