# Community Winget Packaging (winget-pkgs)

This repository publishes installer-first GitHub Releases with these assets:

- `CoolWSL-<version>-win-x64-setup.exe`
- `CoolWSL-<version>-win-x64.msi`
- `CoolWSL-<version>-win-x64.zip`
- `CoolWSL-<version>-win-x64.checksums.txt`

Use the setup EXE asset for the community Winget package. It self-elevates and avoids the current non-elevated Winget MSI handoff failure. The manifest generator falls back to the MSI only for older releases that do not publish the setup EXE.

## One-time setup

1. Fork `microsoft/winget-pkgs`.
2. Clone your fork locally.
3. Ensure `winget` is available on your machine.

Optional: if you enable GitHub Pages for this repo, you can later point `PublisherUrl` and `PackageUrl` to the site. It is not required for winget-pkgs submission.

## Generate manifests from a CoolWSL release

For tagged releases (`vX.Y.Z`), CI now generates `winget-manifests-<tag>` after the GitHub Release is published, deriving checksums from the live release assets.

You can still generate manifests locally when preparing or iterating before submission:

From the CoolWSL repo root:

```powershell
pwsh -NoProfile -File .\build\Export-WingetManifest.ps1 `
  -Version 1.0.4
```

The script defaults to downloading `CoolWSL-<version>-win-x64.checksums.txt` from the tagged GitHub Release so `InstallerSha256` matches the live release installer asset.

For current releases it prefers the published setup EXE and emits a `burn` manifest with self-elevating installer metadata and no external .NET dependency. For older MSI-only releases it falls back to the MSI, reads MSI metadata to populate `Publisher`, `PackageName`, `ProductCode`, and `AppsAndFeaturesEntries`, and validates that the MSI `ProductVersion` matches the requested `-Version`.

Optional: pass `-ChecksumsFile` to force a specific checksums file.

If you use a local checksums file, keep the matching `CoolWSL-<version>-win-x64-setup.exe` beside it for current releases, or pass `-InstallerPath` explicitly. For older MSI-only releases, keep the matching `CoolWSL-<version>-win-x64.msi` beside the checksums file.

This generates files under:

```text
artifacts/winget/manifests/t/tomcoolpxl/CoolWSL/1.0.4/
```

Expected files:

- `tomcoolpxl.CoolWSL.yaml`
- `tomcoolpxl.CoolWSL.installer.yaml`
- `tomcoolpxl.CoolWSL.locale.en-US.yaml`

## Submit to winget-pkgs

1. Copy the generated version folder into your fork of `winget-pkgs` under:
   `manifests/t/tomcoolpxl/CoolWSL/<version>/`
2. Validate:

  ```powershell
  winget validate --manifest .\manifests\t\tomcoolpxl\CoolWSL\1.0.4
  ```

1. Commit and push your branch.
2. Open a pull request to `microsoft/winget-pkgs`.

## Recommended release checklist before opening the PR

1. Confirm the GitHub Release has all four files (`.exe`, `.msi`, `.zip`, `.checksums.txt`).
2. Confirm the setup EXE filename matches `CoolWSL-<version>-win-x64-setup.exe`.
3. Confirm the checksums file contains the setup EXE hash entry.
4. Test install from URL locally after merge (or from your branch with a local manifest) from a standard terminal. The setup EXE is machine-scope but self-elevates when needed:

  ```powershell
  winget install --manifest .\manifests\t\tomcoolpxl\CoolWSL\1.0.4
  ```

## Notes

- Community package publication happens in `microsoft/winget-pkgs`, not in this repository.
- The script uses the release checksums file so the Winget `InstallerSha256` matches release artifacts exactly.