Skip to content

Distribution: offer to handle winget / scoop / Chocolatey packaging #34

Description

@juandresrodca

Hi — TODO.md lists "Distribution - Add to Chocolatey, winget and scoop." I'd like to take this on.

I'd suggest starting with winget, since it needs nothing from you: manifests are community-submitted to microsoft/winget-pkgs and validated by their CI, and the MSI you already attach to releases is exactly what winget's MSI installer type wants (ProductCode + SHA256). I'd submit the manifest for v1.17.0 and keep it updated on future releases — or, if you'd prefer it automated, I can set up a small GitHub Action using wingetcreate that submits the update whenever you publish a release (that route needs a token secret on your side, so it's entirely optional).

After that, scoop's Extras bucket is a natural fit for the portable zip, and Chocolatey is doable too, though it involves a chocolatey.org account/moderation decision that should be yours to make.

Two questions before I start:

  1. Are you happy for me to submit the winget manifest? Any preference on the package identifier (the default convention would be 63BeetleSmurf.PinnyNotes)?
  2. Which channel would you like after that, if any?

Once the manifest is accepted I'd also send a small PR adding a winget install line to the README.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions