Launcher silently providing new sub-versions under same build version with no way to update

[ashlee3dee]

When two users install a build of Blender at different times (for example, 4.3.0 Stable, 1 week apart) there is currently no guarantee that they will be installing the same version of blender.

To Reproduce
Steps to reproduce the behavior:

1. Install a stable version of blender on one machine, then save a file to shared storage.
2. Wait a week
3. Install the same version a week later on a different machine that has access to the shared storage.
4. Open the file made previously
5. Observe version mismatch warning

Expected behavior
Blender launcher should prompt the user to update when the sub-version has been changed, or allow downloading a specific subversion.

Screenshots
Opening a file made by a coworker who downloaded the same version of Blender 1 week after I did. Every file has a version mismatch warning, despite the version and build hash being identical in the launcher.

System (please complete the following information):

• Operation system: Windows 10
• Blender Launcher version: 2.3.2

[Victor-IX]

This will happen when Blender Foundation updates one of the builds on https://download.blender.org/release/.
We have an issue (#85) for adding an update button when an installed build has an available update (new build with the same version or minor version update). This will probably solve your issue.

Note that it's usually not an issue if you save a file with a different version when the only difference is a minor version change or build number change. It can cause data issues when there is a major feature change, and those usually happen between major versions.