Repository navigation
CI: Add WinGet publishing step #2487
sean-r-williams
started this conversation in
Ideas
Replies: 2 comments
|
Homebrew receives special treatment because its maintainer, Rui, is involved with this project. On the other hand, WinGet does not. |
0 replies
|
Yeah, the benefit is too small and the maintenance cost too big. There are plenty of others that would be higher priority (
This is an easy no, we don't want to deal with creating a bot user. It seems like whoever is maintaining the listing could just automate detection and publishing of new releases on a schedule? |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Introduction
Related to #2485.
Windows ships WinGet in-box for package management - packages are added to Microsoft/winget-pkgs by the community, with
wingetbuilt into the OS (Windows 11, Windows Server 2025, Windows 10 version 1809/b17763).The current install instructions only list
choco, which:TFLint is already present on WinGet's package index (as
TerraformLinters.tflint, automatically updated by community bots). Currently, it takes a bit for the PR to get filed by these bots -v0.61.0's release and correspondingwinget-pkgsPR were several hours apart. (v0.60.0took a little over a day.)Proposal
Add first-class support for WinGet package management by programmatically filing PRs to Microsoft/winget-pkgs, akin to
homebrew.ymlThere's prebuilt GitHub Actions for this (like
vedantmgoyal9/winget-releaser), which (with some setup) automatically files PRs given a GitHub PAT and some other configuration options.References
All reactions