Skip to content

Manual Validation: 6/12 Enum update#387274

Closed
stephengillie wants to merge 1 commit into
microsoft:masterfrom
stephengillie:Enum-Update
Closed

Manual Validation: 6/12 Enum update#387274
stephengillie wants to merge 1 commit into
microsoft:masterfrom
stephengillie:Enum-Update

Conversation

@stephengillie

@stephengillie stephengillie commented Jun 12, 2026

Copy link
Copy Markdown
Collaborator

📖 Description

Added JSON file, containing enumeration data. Along with extensive fixes and updates.

✅ Checklist

📦 Manifest Checklist

  • Checked that there aren't other open pull requests for the same manifest update/change
  • This PR only modifies one (1) manifest
  • Validated manifest locally with winget validate --manifest <path> (validation guide)
  • Tested manifest locally with winget install --manifest <path>
  • Manifest conforms to the 1.12 schema

Note: <path> is the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Added JSON file, containing enumeration data. Along with extensive fixes and updates.
@microsoft-github-policy-service microsoft-github-policy-service Bot added the Needs-Attention This work item needs to be reviewed by a member of the core team. label Jun 12, 2026
@microsoft-github-policy-service microsoft-github-policy-service Bot removed the Needs-Attention This work item needs to be reviewed by a member of the core team. label Jun 13, 2026
Process process = new Process();
StreamWriter StandardInput;
StreamReader StandardOut;
ProcessStartInfo processStartInfo = new ProcessStartInfo("PowerShell.exe");

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This also should be winget.exe

Where-Object {`$_ -notmatch 'Microsoft.Windows.Search'} |
Where-Object {`$_ -notmatch 'Microsoft\\Edge\\Application'} |
Where-Object {`$_ -notmatch 'msedge'} |
Where-Object {`$_ -notmatch

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please validate YamlValue results against the manifest schema before using them here, and fail fast on any mismatch. Since this pattern appears in multiple places, it would be better to enforce this centrally anywhere YamlValue is read rather than fixing individual call sites.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a removal section. These lines don't seem to exist in my current version. From the lines, this appars to be the sub-script that is written to disk and run by the VM, so there aren't any YAML values here to validate.

I'll see if I can do this in other sections, where valid.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants