Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please use WinGet Releaser #63

Open
2 of 3 tasks
ppvnf opened this issue Oct 18, 2022 · 2 comments
Open
2 of 3 tasks

Please use WinGet Releaser #63

ppvnf opened this issue Oct 18, 2022 · 2 comments

Comments

@ppvnf
Copy link

ppvnf commented Oct 18, 2022

We are happy to answer your questions about the code or discuss technical ideas.

Please complete the following checklist (by adding [x]):

  • I have searched open and closed issues for duplicates
  • This isn't a feature request
  • This is not a report about my app not working as expected

ProtonVPN is already available on Winget (ProtonTechnologies.ProtonVPN) and it seems up to date, but would it be possible to use WinGet Releaser to make future versions automatically available on Winget?

(As of yet, Winget does not have the ability to carry out such automation natively: microsoft/winget-pkgs#500)

Thanks to vedantmgoyal2009 efforts, ProtonVPN now is automatically updated on Winget, but this isn't ideal because:

  • Sometimes automation may go offline for maintenance, hence it is better to use GitHub Action. It is also easier to maintain and implement new features in the action. All apps use the latest manifest schema and fields.

  • Automation is generally preferred for non-GitHub packages (meaning: software which are hosted on GitHub) that cannot take advantage of the GitHub Action.

  • Since all GitHub API requests are authenticated with my account, using action distrubutes the amount of traffic on GitHub. The action is triggered automatically on releases, so we don't need to fetch APIs or scrape webpages to check for updates periodically, and PRs are created with the software's developer account.

  • Microsoft prefers publishers managing releases for their apps themselves instead of a third party. It isn't a hard-and-fast rule, note the word "prefers" here.

@vedantmgoyal9
Copy link

cc @kaplun @kylekatarnls

@9at8
Copy link

9at8 commented Jul 1, 2023

+1 it's already out of date

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

No branches or pull requests

3 participants