-
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
New version: PolarGoose.ShowWhatProcessLocksFile version 6.0 #153131
New version: PolarGoose.ShowWhatProcessLocksFile version 6.0 #153131
Conversation
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
=== manifests\p\PolarGoose\ShowWhatProcessLocksFile\6.0 === |
Hi @PolarGoose, This manifest removes Apps and Features entries that are present in previous PR versions. These entries should be added to this version, to maintain version matching, and prevent the 'upgrade always available' situation with this package. (Automated response - build 880.) |
@stephengillie, |
Oh - this is referring to the The previous PR had: AppsAndFeaturesEntries:
- ProductCode: '{2D35E2E6-3FE3-4D1E-9B94-8352495D1A35}'
UpgradeCode: '{ECBB21BF-5B26-4971-AAC2-D3528A7F10FB}' Should these values be added to this manifest? If not, it's okay. |
It is ok not to add them. These fields are optional. |
Edit: Sorry, using the wrong automation tool. |
360954f
into
microsoft:master
Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present. |
Checklist for Pull Requests
Manifests
winget validate --manifest <path>
?winget install --manifest <path>
?Note:
<path>
is the name of the directory containing the manifest you're submitting.Microsoft Reviewers: Open in CodeFlow