GoogleChrome package v145 installs v144.

[heylanwe64]

Checklist

• I have verified that this is the correct repository, and the package is maintained by the chocolatey-community user.
• I have verified that this is happening in the latest available version of the package.

Chocolatey Version

2.5.1

Chocolatey License

None

Package Version

145.0.7632.26

Current Behaviour

When installing latest package version Google Chrome which is 145.0.7632.26 currently the Event Viewer claims it is actually 144.0.7559.110. This is causing all sorts of version mismatch (ex. ChromeDriver).

Expected Behaviour

No response

Steps To Reproduce

1. Run choco upgrade googlechrome chromedriver -y -f
2. Check version of google chrome in windows

googlechrome version did not upgrade. It breaks CI flows.

Environment

- Operating System: W11
- PowerShell Version: 5.1.26100.7627
- Shell: choco upgrade googlechrome chromedriver -y -f

Chocolatey Log

Full log in the attachment.

Anything else?

chocolatey.log

[github-actions]

Thanks for raising this issue!

The packages within this repository are maintained by a small team of volunteer Community Maintainers, in their own time. Their time, like yours is important. Please help them by not wasting it.

This is a community repository where the expectation is that everybody will get involved by raising pull requests to fix problems they find. This will also allow that problem to be fixed more quickly as you don't have to wait for a member of the Community Maintainer Team to pick it up.

If you are unable to fix the issue yourself, the Community Maintainers Team will look at it when time allows. There are no service level agreements, nor should there be any expectation on when people can resolve issues in their own time.

A few dos and don'ts:

• Do provide as much information as you can in any issue that you raise.
• Don't complain that an issue has not yet been picked up or resolved. You are expected to help out in this community maintained repository. If you are unable to do so, don't complain when others don't adhere to your timelines. There is no SLA nor should you have any expectation of one.
• Do read the CONTRIBUTING and COMMITTERS documentation before raising a pull request as it contains valuable information on what automation is used in this repository.
• Do read the Code of Conduct.
• Don't post your frustration in comments. The Community Maintainers Team are not a punching bag for your frustration. You will only end up banned from the repository.

Thank you.
(Automatically posted message)

[heylanwe64]

Even without ignore checksum, the result is the same. Version is not correct.