Add Windows Package Manager (Winget) distribution support

[Copilot]

Enables distribution via winget install ScottHanselman.WindowsEdgeLight once submitted to microsoft/winget-pkgs.

Manifest Files

• Created v1.10.0 schema manifests in manifests/s/ScottHanselman/WindowsEdgeLight/0.6.0/
• Configured as portable app (zip → exe) supporting x64 and ARM64
• Template includes placeholder SHA256 hashes with inline comments

Automation

update-winget-manifest.ps1: Downloads release artifacts, calculates hashes, generates manifests, validates against placeholders

.\update-winget-manifest.ps1 -Version "0.7.0"
# Outputs: 3 manifest files with correct SHA256 hashes

Documentation

• docs/WINGET.md: Submission methods (WingetCreate, manual, YamlCreate)
• docs/WINGET_AUTOMATION.md: GitHub Actions workflows for auto-submission
• WINGET_QUICKSTART.md: Maintainer quick reference

Updates

• README.md: Added Winget as installation Option 1
• .gitignore: Excludes temp/ and *.tmp from manifest script

Submission Workflow

# Method 1: Auto-submit with WingetCreate
wingetcreate update ScottHanselman.WindowsEdgeLight \
  --urls <x64-url> <arm64-url> \
  --version X.Y.Z \
  --submit

# Method 2: Generate locally, submit manually
.\update-winget-manifest.ps1 -Version "X.Y.Z"
# Copy manifests to winget-pkgs fork, create PR

Original prompt

How would I add this to Winget

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[shanselman]

Triage note: This Winget manifest/automation PR looks useful but needs review before merging. Key questions: Are the manifest templates correct for our current release structure? Do the SHA256 placeholder hashes get updated by the script? Leaving open for review.

[github-actions]

🤖 This is an automated response from Repo Assist.

Hi @shanselman — addressing the two questions from your triage note:

✅ Are the manifest templates correct for the current release structure?

Yes, the structure is correct. The manifests use InstallerType: zip + NestedInstallerType: portable pointing to WindowsEdgeLight.exe inside the zip — that matches the PublishSingleFile self-contained build and the zip-based release artifacts perfectly.

✅ Do the SHA256 placeholder hashes get updated by the script?

Yes. update-winget-manifest.ps1 downloads the release zips from GitHub, computes their SHA256 hashes, and writes them into the manifest files — replacing the YOUR_SHA256_HASH_HERE placeholders. It is safe to merge the PR as-is (the placeholders are clearly labelled "DO NOT submit to winget-pkgs with placeholder hashes").

⚠️ Version mismatch — manifests target v0.6.0, latest release is v1.11.0

The manifests committed in this PR target 0.6.0, but the latest GitHub release is v1.11.0. Before submitting to microsoft/winget-pkgs, you'd need to run the script for the current version. Since the release assets are already on GitHub, here are the ready-to-use hashes:

Architecture	SHA256
x64	c37a4d0b7e21caaf298e7c1ed343a035d1e8159a600afcfd3dd721b717edad16
arm64	33470b50623d6c8dd9f8841cad7810238eed478c673b1daf6f780d5db7fe7065

To regenerate manifests locally (or in CI) for v1.11.0:

.\update-winget-manifest.ps1 -Version "1.11.0"

Or to submit directly with WingetCreate:

wingetcreate update ScottHanselman.WindowsEdgeLight `
  --urls "https://github.com/shanselman/WindowsEdgeLight/releases/download/v1.11.0/WindowsEdgeLight-v1.11.0-win-x64.zip" `
         "https://github.com/shanselman/WindowsEdgeLight/releases/download/v1.11.0/WindowsEdgeLight-v1.11.0-win-arm64.zip" `
  --version 1.11.0 `
  --submit

Recommendation: Merge this PR (it adds the infrastructure and docs), then run the script / WingetCreate command above to submit v1.11.0 to microsoft/winget-pkgs.

Note

🔒 Integrity filter blocked 2 items

The following items were blocked because they don't meet the GitHub integrity level.

• Detect camera is being used by another application and automatically turn on #21 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #26 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by Repo Assist · ● 728.7K · ◷

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@cbb46ab386962aa371045839fc9998ee4e97ca64