You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 6, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Feb 6, 2026. It is now read-only.
winget-pkgs CI handles the rest - When we submit a PR to microsoft/winget-pkgs, their automation:
Verifies installer URLs are accessible
Downloads and verifies SHA256 hashes
Installs in a Windows VM
Runs security scanning
Local install testing is impractical - winget's --manifest flag doesn't support file:// URLs, requiring an HTTP server setup which is overengineered for what we need
Windows binary already tested - The Chocolatey CI builds and runs cfl.exe on Windows, so we know the binary works
Next step
Issue #77 tracks the actual submission to microsoft/winget-pkgs once we have a release to publish.
Activity
rianjs commentedon Jan 17, 2026
Implementation Plan
Package Location
Manifest Details
1. Version Manifest (
OpenCLICollective.cfl.yaml)2. Installer Manifest (
OpenCLICollective.cfl.installer.yaml)Uses
InstallerType: zipwithNestedInstallerType: portablefor the single binary.Key points:
NestedInstallerFiles.RelativeFilePath=cfl.exe(binary is at root of zip)PortableCommandAlias=cfl(command users type)3. Locale Manifest (
OpenCLICollective.cfl.locale.en-US.yaml)Publishing Process (README.md)
winget validate --manifest <path>manifests/o/OpenCLICollective/cfl/<version>/Alternative: Use wingetcreate:
Verification
The zip structure from GoReleaser:
Only
cfl.exeneeds to be referenced inNestedInstallerFiles- Winget will extract and create the command alias.feat: add Winget manifest templates for Windows distribution
rianjs commentedon Jan 17, 2026
Implementation Complete
Added Winget manifest templates in PR #76. Here's where we landed:
What's included
cflcommand aliasCI approach
We went with schema validation only rather than full install/uninstall testing. Here's why:
Schema validation catches our errors - YAML syntax, missing required fields, malformed URL patterns
winget-pkgs CI handles the rest - When we submit a PR to microsoft/winget-pkgs, their automation:
Local install testing is impractical - winget's
--manifestflag doesn't supportfile://URLs, requiring an HTTP server setup which is overengineered for what we needWindows binary already tested - The Chocolatey CI builds and runs
cfl.exeon Windows, so we know the binary worksNext step
Issue #77 tracks the actual submission to microsoft/winget-pkgs once we have a release to publish.
feat: add Winget manifest templates for Windows distribution (#76)