-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Add UpgradeBehavior deny #3512
Add UpgradeBehavior deny #3512
Conversation
We would have the work in the client and the schema here, as well as the REST schema and the docs at winget-pkgs. |
cc @ryfu-msft |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
There are a couple e2e tests related to portable failed because of this new addition of portable 4.0.0.0 manifest with upgrade deny. We should probably create a new package identifier (2 manifests) like AppInstallerTest.TestUpgradeDeny so it's isolated and not affecting other tests. |
Makes sense; I'll take a look |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@ryfu-msft - I took a look at the pester tests and I don't see any reason why the BuildPowerShellModule tests would be failing, especially when I didn't touch anything about the PowerShell modules or COM, and it seems like the pipelines are showing a COM error. Unless the changes to the SharedLib files are interfering somehow?
|
This seems like a transient error, lets see if the rerun fixes it. You must be lucky today 😄 |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-cli/pull/3512&drop=dogfoodAlpha