Skip to content

ci: auto-publish MSI installers to winget-pkgs - #496

Open
k9fr4n wants to merge 1 commit into
ConSol-Monitoring:mainfrom
k9fr4n:feature/winget-upstream
Open

k9fr4n wants to merge 1 commit into
ConSol-Monitoring:mainfrom
k9fr4n:feature/winget-upstream

Conversation

@k9fr4n

@k9fr4n k9fr4n commented Nov 9, 2026

Copy link
Copy Markdown

Hi there!

Following up on the request in #175 to make SNClient easier to install and keep up to date on Windows, this PR adds automatic publishing to Winget.

Winget is the default package manager on Windows: it ships with App Installer on Windows 11, modern Windows 10 (1809 and later), and Windows Server 2025 (see Microsoft Learn). Publishing SNClient there covers stock Windows installs with no extra tooling for users.

What this does:

  • Adds a small Publish to Winget workflow based on vedantmgoyal9/winget-releaser
  • On each published (stable) release, it submits the 3 MSI installers to microsoft/winget-pkgs as ConSolMonitoring.SNClient
  • It can also be triggered manually for an existing tag, handy for the very first submission

Once merged, users will be able to run winget install ConSolMonitoring.SNClient and get updates automatically.

One-time setup for maintainers after merge:

  • Fork microsoft/winget-pkgs with the account owning the token
  • Create a classic PAT with public_repo scope
  • Add it as WINGET_TOKEN repository secret
  • Run the workflow once manually (e.g. with the latest tag) and merge the created winget-pkgs PR

@inqrphl

inqrphl commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Hello, thanks for the contribution.

I will review and merge this if we decide to merge winget support using #490 first.

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.

2 participants