-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Fixed UpgradeBehavior for Edge WebView2 version 96.0.1054.53. #39467
Conversation
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @wingetbot! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
Hello @jedieaston, |
Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present. |
@jedieaston, I've been chatting with the Edge team. Can you shed a bit of light on why you changed the upgrade behavior to "uninstall previous"? |
In my testing, WebView2 wouldn't upgrade if it detected that a previous version was already installed (I assumed because it is supposed to be updated automatically in the background). The only way I was able to upgrade it if a existing version was installed was to uninstall the previous version. Testing it now, it seems like I can't reproduce that behavior anymore. Maybe they fixed it? |
There may be a few different packages attempting to use WebView2, and it is intended to "keep itself upgraded". We're talking with the team about publishing manifests themselves and taking advantage of Enhancements to upgrade (Apps that upgrade themselves). |
That would be awesome! Especially if they could cover the other Edge channels. |
winget validate --manifest <path>
?winget install --manifest <path>
?Note:
<path>
is the name of the directory containing the manifest you're submitting.Technically resolves microsoft/winget-cli#1824
Microsoft Reviewers: Open in CodeFlow