Due to the way that Drupal 8's versioning now works, the latest version isn't necessarily the latest version that the site should update to (as it was with Drupal 7). For example, Drupal will have versions available of 8.5.x and 8.6.x. Although 8.6.x is the latest version which sites should be updated to sites may not be updated immediately to that minor release.
When a security update is then released, the security team have released a security release for both 8.6.x as well as 8.5.x. This means that although the sites running the latest 8.5.x version, Warden is still showing the sites as needing a security update. This is due to the latest version (8.6.x) also being a security release.
Warden therefore needs to be able to know which minor version of Drupal 8 a site is running to know if it is running the latest release of that minor version that contains a security release, rather than just checking if it is less that the latest release which has a security update.
Due to the way that Drupal 8's versioning now works, the latest version isn't necessarily the latest version that the site should update to (as it was with Drupal 7). For example, Drupal will have versions available of 8.5.x and 8.6.x. Although 8.6.x is the latest version which sites should be updated to sites may not be updated immediately to that minor release.
When a security update is then released, the security team have released a security release for both 8.6.x as well as 8.5.x. This means that although the sites running the latest 8.5.x version, Warden is still showing the sites as needing a security update. This is due to the latest version (8.6.x) also being a security release.
Warden therefore needs to be able to know which minor version of Drupal 8 a site is running to know if it is running the latest release of that minor version that contains a security release, rather than just checking if it is less that the latest release which has a security update.