[Zip][Portable] BurntSushi.ripgrep.GNU 13.0.0

[Trenly]

• Have you signed the Contributor License Agreement?
• Have you checked that there aren't other open pull requests for the same manifest update/change?
• Have you validated your manifest locally with winget validate --manifest <path>?
• Have you tested your manifest locally with winget install --manifest <path>?
• 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

[Trenly]

@msftbot zip

[wingetbot]

   

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

Hello @Trenly,

The package manager bot determined that the metadata was not compliant.

Please verify the manifest file is compliant with the package manager 1.2 manifest specification.
Make sure the ID is of the form publisher.appname and that the folder structure is manifests\partition\publisher\appname\version.
Note: The path and "PackageIdentifier" are case sensitive.
Be sure to use a tool like VSCode to make sure the manifest YAML syntax is correct.

You could also try our Windows Package Manager Manifest Creator or the YamlCreate script.

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

Template: msftbot/validationError/manifest/metadata

[wingetbot]

/AzurePipelines run

[azure-pipelines]

There was an error handling pipeline event ea7755b1-87b1-40fc-bdd5-db6a3c646a84.

[wingetbot]

/AzurePipelines run

[azure-pipelines]

There was an error handling pipeline event 0a5b5f56-5c1c-4597-a480-fb3f3ff8b706.

[Trenly]

@wingetbot run

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

Hello @Trenly,

The pull request encountered an internal error and has been assigned to a developer to investigate.

Template: msftbot/validationError/internalError

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[stephengillie]

@wingetbot waivers Add Validation-Executable-Error

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[wingetbot]

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

[adigitoleo]

Can't find the entry point on windows 11. Tried both GNU and MSVC installs. No 'rg', 'ripgrep' or similar, can't even see the directory in Program Files. Am I doing it wrong?

Edit: Found the directory, under Microsoft > WinGet > Packages. It is added to path but the problem is that the .exe resides in another level of nested directory and is not copied out of there.

[sitiom]

Edit: Found the directory, under Microsoft > WinGet > Packages. It is added to path but the problem is that the .exe resides in another level of nested directory and is not copied out of there.

Workaround: Enable developer mode. Corresponding issue:

• Root directory of portable packages is always added to the PATH regardless of RelativeFilePath winget-cli#2909