New package: Microsoft.DebugDiag version 2.3.0.38

[Dragon1573]

Checklist for Pull Requests

• Have you signed the Contributor License Agreement?
• Resolve [Package Request]: Add Debug Diagnostic Tool v2 Update 3 #172870

Manifests

• Have you checked that there aren't other open pull requests for the same manifest update/change?
• This PR only modifies one (1) manifest
• Have you validated your manifest locally with winget validate --manifest <path>?
• Have you tested your manifest locally with winget install --manifest <path>?
  • See [Package Request]: Add Debug Diagnostic Tool v2 Update 3 #172870 (comment)
• Does your manifest conform to the 1.6 schema?

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

---

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

   

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[stephengillie]

Verify:

I'm not sure why the help file shows 2.1 instead of 2.3.0.38. I'm guessing that the help file is out of date, and was written for the previous application version. I couldn't see the version number displayed anywhere else.

[wingetbot]

Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present.

[MagicAndre1981]

thanks for the PR 👍