New version: charmbracelet.wishlist 0.12.0

[charmcli]

• 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.4 schema?

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

---

Automated with GoReleaser

Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/111956&drop=dogfoodAlpha

[wingetbot]

   

[wingetbot]

/AzurePipelines run

[azure-pipelines]

No commit pushedDate could be found for PR 111956 in repo microsoft/winget-pkgs

[wingetbot]

/AzurePipelines run

[azure-pipelines]

No commit pushedDate could be found for PR 111956 in repo microsoft/winget-pkgs

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[charmcli]

@microsoft-github-policy-service agree [company="Charmbracelet, Inc"]

[charmcli]

@microsoft-github-policy-service agree company="Charmbracelet, Inc"

[stephengillie]

@wingetbot waivers Add Validation-Executable-Error

[wingetbot]

/AzurePipelines run

[azure-pipelines]

No commit pushedDate could be found for PR 111956 in repo microsoft/winget-pkgs

[caarlos0]

No commit pushedDate could be found for PR 111956 in repo microsoft/winget-pkgs

What does this mean?

[Trenly]

@wingetbot run

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[microsoft-github-policy-service]

charmcli,

The check-in policies require a moderator to approve PRs from the community.

Our moderators are community volunteers, please be patient and allow them sufficient time to review your submission.

Template: msftbot/requiresApproval/moderator

[wingetbot]

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