Add PowerShell 7.2.7 and 7.0.13 manifests

[anamnavi]

• [x] Have you signed the Contributor License Agreement?
• [x] Have you checked that there aren't other open pull requests for the same manifest update/change?
• [x] Have you validated your manifest locally with winget validate --manifest <path>?
• [x] Have you tested your manifest locally with winget install --manifest <path>?
• [x] Does your manifest conform to the 1.2 schema?

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

---

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

   

[wingetbot]

/AzurePipelines run

[azure-pipelines[bot]]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

Hello @anamnavi,

The package manager bot determined there was an issue with the pull request. Make sure the manifest files are under the manifests\partition\publisher\appname\version directory and only one package version is being modified in your PR. The partition of the path must be the first letter of the publisher in lower-case.

Example: Path: manifests / m / Microsoft / WindowsTerminal / 1.6.10571.0 / WindowsTerminal.yaml

For details on the error, see the details link below in the build pipeline.

You may also try the Windows Package Manager Manifest Creator

Template: msftbot/validationError/pullRequest

[ghost]

Hello @anamnavi,

The package manager bot determined changes have been requested to your PR.

Template: msftbot/changesRequested

[ghost]

Hello @anamnavi,

The PR could not be validated because there is a merge conflict which adds bad characters to the manifest. Please address the merge conflict and resubmit.

Template: msftbot/mergeConflict