@mcnesium opened this Issue on December 11th 2018

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 in CHANGELOG.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?

@Findus23 commented on December 11th 2018 Member

Hi,

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.

For checking the latest version of Matomo, please use the API:
https://api.matomo.org/1.0/getLatestVersion/

Or check the https://builds.piwik.org/LATEST file.

If you want to find out the version of a Matomo folder, please use the core/Version.php file:

https://github.com/matomo-org/matomo/blob/a06e2d5c27e0172b6de647c6754b9eead5ed0b36/core/Version.php#L23

@tsteur commented on December 11th 2018 Member

If you want to know the current version of your Matomo, please fetch the API method API.getMatomoVersion see https://developer.matomo.org/api-reference/reporting-api

This Issue was closed on December 11th 2018
Powered by GitHub Issue Mirror