-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
[Package Issue]: Google.Chrome trying to update from stable to beta #139781
Comments
Related #139144 |
Also noting that the sha and product code for 122.0.6261.39 and 121.0.6167.184 are both the same in this repo but previous versions (ex: 121.0.6167.161) are different. winget-pkgs/manifests/g/Google/Chrome/122.0.6261.39/Google.Chrome.installer.yaml Lines 26 to 46 in 591769a
winget-pkgs/manifests/g/Google/Chrome/121.0.6167.184/Google.Chrome.installer.yaml Lines 26 to 46 in 591769a
winget-pkgs/manifests/g/Google/Chrome/121.0.6167.161/Google.Chrome.installer.yaml Lines 26 to 46 in 591769a
|
It's not a beta version but a so-called "early stable" version: https://chromereleases.googleblog.com/2024/02/early-stable-update-for-desktop.html I have never seen direct links to early stable versions. |
Since this seems to be causing install loops, would the correct move be to remove 122.0.6261.39 until it is no longer "early"? Or is there another way to resolve the issue outside of waiting for the update to be more widely available? Also note that Google Chrome itself does not seem to update to 122.0.6261.39 via its about page, at least for me. |
Exactly. I don't understand what is taking so long.
A publicly available stable version will usually have a bigger version number.
For a small percentage of users it does. |
Hey all, the bot pulls the version from https://versionhistory.googleapis.com/v1/chrome/platforms/win/channels/stable/versions?order_by=version%20dsc Looking into if this is a once off issue from Chrome dropping the version and then holding off or if something else. |
Since this issue is specific to Google Chrome, and it's now updated twice correctly since then, I guess it should be closed. I'm assuming Google just messed up the file they used to list versions. Of course, I'm assuming it's working correctly for other people now, too. |
Please confirm these before moving forward
Category of the issue
Other
Brief description of your issue
For the last several days, "winget upgrade" has been giving me the following:
"Name Id Version Available Source
Google Chrome Google.Chrome 121.0.6167.185 122.0.6261.39 winget
1 upgrades available."
According to this page:
https://googlechromelabs.github.io/chrome-for-testing/
and the Chrome browser, itself, my installed version (121.0.6167.185) is the latest stable version. The version winget is trying to get me to install (122.0.6261.39) is the latest beta. Unless I'm misunderstanding something, winget is trying to to upgrade my stable version of Chrome with a beta version. That shouldn't happen.
Steps to reproduce
Actual behavior
Winget is saying there's a newer version of Chrome available. But, it's a beta, not a stable version.
Expected behavior
Winget should only suggest stable upgrades for stable products.
Environment
Screenshots and Logs
No response
The text was updated successfully, but these errors were encountered: