update Miller.Miller to 6.12.0 (#136590)

[rursprung]

the manifest has been created using the following command:

wingetcreate update miller.miller -v 6.12.0 -u https://github.com/johnkerl/miller/releases/download/v6.12.0/miller-6.12.0-windows-386.zip https://github.com/johnkerl/miller/releases/download/v6.12.0/miller-6.12.0-windows-amd64.zip

the ReleaseNotesUrl has been manually added as wingetcreate update does not yet support release notes (see also
microsoft/winget-create#497).

• Have you signed the Contributor License Agreement?
• 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>?
• Does your manifest conform to the 1.6 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]

Azure Pipelines successfully started running 1 pipeline(s).

[rursprung]

@johnkerl: it'd be great if johnkerl/miller#1459 could be implemented so that this were automated (it should be fairly easy to set up, but it's something you have to do yourself due to the required access token in the workflow). thanks!

[stephengillie]

Automatic Validation ended with:

Executable C:\Users\validator\AppData\Local\Microsoft\WinGet\Links\mlr.exe returned exit code: 1
Executable C:\Users\Validator\AppData\Local\Microsoft\WinGet\Links\mlr.exe returned exit code: 1

(Automated response - build 870.)

[rursprung]

Automatic Validation ended with:

Executable C:\Users\validator\AppData\Local\Microsoft\WinGet\Links\mlr.exe returned exit code: 1
Executable C:\Users\Validator\AppData\Local\Microsoft\WinGet\Links\mlr.exe returned exit code: 1

(Automated response - build 870.)

this is to be expected if mlr is being called w/o any arguments and not a packaging problem.

[stephengillie]

@wingetbot waivers Add Validation-Executable-Error

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[stephengillie]

this is to be expected if mlr is being called w/o any arguments and not a packaging problem.

This situation is common. Thanks for your patience.

[wingetbot]

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