about winget integration

[MerrickZ]

Hi there, it's been a long time.
I'm currently working on automatically winget submission when new release is published via Github Actions, should be able to PR in this weekend.

Pros?

When this is done, winget registry will be automatically updated after new release published.

Why?

Currently, winget entries are manually maintained by @stevenlele and me, there maybe some cons about version delay, incorrect zip file download urls, etc.

Github Actions and Powershell could help, make it automatically happen.

Details?

1st, @zufuliu should generate a classic token with public_repo enabled, and write it in this repo's settings/secrets.

then, Github Actions will run when new release version is published.

Next?

I think that's possible to maintain pre-release versions in future after each commit

Cons?

winget still can't generate shortcuts / start menu entries, or perform version upgrade when ini file changed in local. You still need to use --force when upgrade via winget.

[stevenlele]

Hi, I'm already maintaining an automation at https://github.com/stevenlele/winget-update/blob/main/notepad4.py (which runs every hour to check for updates) and you can see the automated submissions at microsoft/winget-pkgs#173422 and microsoft/winget-pkgs#173423. I'm not sure if your work will conflict with this one.

[MerrickZ]

Great work!
I've read some yml from your submissions, Are you running that script every hour to check for new releases?
Saw cron 5 * * * * in your actions.
I'm working on make it run on the event of release, maybe better?

[stevenlele]

I don't see much of a difference.

Maintaining it inside the repo will:

• Increase the burden of the core developer as they might need to learn some WinGet details when the workflow fails or something changed from the WinGet side
• In case they need to revoke/re-release a version (in a short time), there need to spend extra effort to remove/revert the submitted manifests

Since I'm maintaining multiple automated manifests submissions, I can take care of errors and issues more efficiently.

[MerrickZ]

Well, I've noticed there're some mistakes in winget entries, can you correct these?

See? there're extra HD in every x64 entries.

[stevenlele]

These are correct. HiDPI builds are used if available on any architecture. They provide clearer icons on HiDPI screens.