Skip to content

ci: publish signed MSI to winget on release#15

Merged
AThraen merged 1 commit into
mainfrom
feat/winget-publish
May 10, 2026
Merged

ci: publish signed MSI to winget on release#15
AThraen merged 1 commit into
mainfrom
feat/winget-publish

Conversation

@AThraen
Copy link
Copy Markdown
Contributor

@AThraen AThraen commented May 10, 2026

Summary

  • New workflow .github/workflows/winget.yml submits the signed MSI to microsoft/winget-pkgs as UmageAI.CodeShellManager after each release.
  • Triggers on release: released (auto) and workflow_dispatch with a tag input (manual backfill / retry).
  • Uses vedantmgoyal9/winget-releaser@v2.

Requires before this works

  • Repo secret WINGET_TOKEN — a classic GitHub PAT with public_repo scope. Fine-grained tokens are not yet supported by the action.

Backfilling v0.4.0

v0.4.0 was released before this workflow existed, so the release event won't fire for it. Once the secret is set, dispatch the workflow manually:
```
gh workflow run winget.yml -f tag=v0.4.0
```
The action submits a PR to microsoft/winget-pkgs; review/merge happens on Microsoft's side and typically lands within a day.

Test plan

  • Add WINGET_TOKEN secret in repo settings
  • Manually dispatch with tag=v0.4.0 to seed the package on winget-pkgs
  • Confirm Microsoft's bot accepts the PR
  • On next tagged release, verify the workflow fires automatically and submits the bump

🤖 Generated with Claude Code

Adds .github/workflows/winget.yml — fires on the `release: released`
event and submits the MSI to microsoft/winget-pkgs as
UmageAI.CodeShellManager via vedantmgoyal9/winget-releaser. Also
workflow_dispatch-able with a `tag` input to backfill or retry.

Requires repo secret WINGET_TOKEN (classic PAT, public_repo scope).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@AThraen AThraen merged commit 0943470 into main May 10, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant