-
-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Google Chrome Incorrect Version Number #574
Comments
Confirmed here as well just now: The version of GoogleChrome Stable x64 msi reported by Get-EvergreenApp is 119.0.6045.59 but the downloadeded .msi is version 118.0.5993.118 (which the Chrome download site reports as the correct stable channel version). PS > Get-EvergreenApp googlechrome Version : 119.0.6045.59 Version : 119.0.6045.59 Version : 120.0.6091.0 Version : 120.0.6073.0 Version : 120.0.6073.0 Version : 118.0.5993.118 Version : 118.0.5993.118 Version : 119.0.6045.59 Version : 119.0.6045.59 Version : 119.0.6045.59 |
The issue is that |
The stable and beta version have the same version number. 119.0.6045.200 is the correct version for the stable release.
|
IMHO I think Evergreen is working exactly as it should in this case. My other bug bear is that Google often decide to release two different version numbers at the same time - most recent example: https://chromereleases.googleblog.com/2023/11/stable-channel-update-for-desktop_28.html |
I have found today that the stable version is 120.0.6099.109 (or .110) where as the extended version is 120.0.6099.110, (https://chromereleases.googleblog.com/2023/12/stable-channel-update-for-desktop_12.html)
Unsure if this helps anyone else, But in my case I don't really care whether it's the stable or extended channel - I just want the latest version of either.
If this still doesn't solve the version number reliability, I may resort to a sanity check of the downloaded msi file using Get-FileMetaData
|
I just hit this issue today also... Stable/Extended showing as 122.0.6261.69 and 122.0.6261.70 respectively, but both from the same URL (which downloads the Extended one ending in .70). I guess I could just switch to using the Extended channel if this is always the version that gets served up by the fixed URL, but I will have to test that over a time period to see if it's viable. |
Unfortunately for us where we need consistency - The manner in which Google publish their meta data will always be wrong, especially when they release multiple 'Stable Release' versions at the same time. I'm sure Google have their reasons (??!?), but it just seems madness where we need some consistency. |
Yep - Entirely expected |
These updated URLs though, won't change the status of this issue - there is no Extended installer and there doesn't appear to be a way to return a URL with a specific version of the installer. Evergreen is returning a URL to a download similar to the official download page here: https://chromeenterprise.google/browser/download/#windows-tab I've removed the bug label from this issue, because this isn't a bug. |
The API for self-updating or downloading the installer used by the downloader on https://www.google.com/chrome/ returns the correct version. Even if the API is not for the enterprise MSI installer, both of them are updated to the same version almost at the same time according to my automation records.
|
Update Chrome data with start date for each channel
Here's an update to
|
Maybe the issue subject could also be amended to remove the '[Bug]: ' prefix? |
What happened?
The Evergreen module lists the latest Stable x64 msi version as 118.0.5993.117 but when it downloads and I check the properties, it is listed as 118.0.5993.118
Version
2310.868
What PowerShell edition/s are you running Evergreen on?
Windows PowerShell
Which operating system/s are you running Evergreen on?
Windows 10+
Have you reviewed the documentation?
Verbose output
The text was updated successfully, but these errors were encountered: