Request GitHub pkgs to move to WinGet Releaser Action

[vedantmgoyal9]

This issue is used to track the status of issues created on repos to request developers to implement https://github.com/marketplace/actions/winget-releaser in their release workflow.

Packages should be removed from the automation here, once the software maintainers implement the action, in order to avoid duplicate update PRs at microsoft/winget-pkgs repo.

Add new package identifier at: https://forms.gle/4qkTFUuJVbTtAUGd9

See shared google spreadsheet: https://docs.google.com/spreadsheets/d/1dnTRsRI8JdTyHibbBy8b1-Odd1gHJRjScm_KWUQ-jHk/edit?usp=sharing

Edit: Added spreadsheet and google form links.

[vedantmgoyal9]

@ppvnf you can add package identifier and issue URL here, so that I can track its status and once a repo adds winget releaser, the package can be removed from the automation to avoid duplicate PRs at winget-pkgs repo.

[ppvnf]

How about using some script to find packages that use download links from Github?

[vedantmgoyal9]

You can surely do that, but make sure the project is still maintained. WinGet contains about ~40% (a roughly estimated value 😅) projects which are no longer receive updates and/or are archived.

[ppvnf]

You can surely do that, but make sure the project is still maintained. WinGet contains about ~40% (a roughly estimated value 😅) projects which are no longer receive updates and/or are archived.

list github.txt

I am thinking about reading the list and adding here the packages I easily recognize as active projects (after a little bit of search). Unless you have a better idea. Also, I think it will get confusing here. What about creating a shared spreadsheet?

[vedantmgoyal9]

I am thinking about reading the list and adding here the packages I easily recognize as active projects (after a little bit of search). Unless you have a better idea. Also, I think it will get confusing here. What about creating a shared spreadsheet?

Yeah, I guess creating a Google Spreadsheet would be better.

Sorry, no time/patience for the whole list. I will search only my favorite apps

No problem. Even a few packages will work, so that I'll not hit rate-limits due to the automation.

[SpecterShell]

Nikse.SubtitleEdit: https://github.com/SubtitleEdit/subtitleedit/releases

They're using wingetcreate already, so no further automation is needed.

[dpprdan]

• Bitwarden.Bitwarden: Please use WinGet Releaser bitwarden/clients#3816

Since they closed the issue already and referred to the forum and @ppvnf apparently was referred to the GH issues from the forum, it might be faster/easier to open a PR adding the winget-releaser to their https://github.com/bitwarden/clients/blob/master/.github/workflows/release-desktop.yml. It already contains steps for snap and chocolatey.

[SpecterShell]

maojindao55.Etcder: https://github.com/maojindao55/etcder/releases
MoyuScript.DoubleMouseDownloader: https://github.com/MoyuScript/double-mouse-downloader/releases
HamsterBase.HamsterBase: https://github.com/hamsterbase/hamsterbase/releases
Serverless.Serverless: https://github.com/serverless/serverless/releases
Tencent.COSCLI: https://github.com/tencentyun/coscli/releases
BartoszCichecki.LenovoLegionToolkit: https://github.com/BartoszCichecki/LenovoLegionToolkit/releases
Tauri.create-tauri-app: https://github.com/tauri-apps/create-tauri-app
z4yx.GoAuthing: https://github.com/z4yx/GoAuthing/releases
Rizonesoft.Notepad3: https://github.com/rizonesoft/Notepad3/releases
yt-dlp.yt-dlp: https://github.com/yt-dlp/yt-dlp/releases
XmacsLabs.Mogan: https://github.com/XmacsLabs/mogan/releases

[ppvnf]

@vedantmgoyal2009 What about Microsoft packages?

Some are updated by wingetbot and others by you

[vedantmgoyal9]

You can create issues for them, and add them to spreadsheet using the form. I hope they will accept to use winget-releaser.

[ppvnf]

microsoft/winget-pkgs#87731