XYplorer Beta Club

I recently started using a program called UpdateHub to keep my Windows programs up to date (https://github.com/NexovaDev/UpdateHub/releases).
Apparently it uses a central repository of programs to know what programs require updating, as described here.

https://github.com/NexovaDev/UpdateHub/discussions/282
and
https://github.com/microsoft/winget-pkg ... -a-package


It sure would be nice if XYPlorer could be added to the repository, especially if the one repository is accessible by multiple updater programs. I have no idea if this is a big ask or a little ask - it's somewhat over my head, but this seemed like the most appropriate location for posting. I'm a long-time XYPlorer user, and happy owner of a lifetime licence.

Thanks, but at first glance it looks like a lot of work for little gain.

It's there finally! Took me some time to get it right. Now both portable and install versions are available on WinGet.

Wow, thanks!

Do you have to work again with each update release?

hi! nice work adding it.

for those of us that use winget for updates but do not want to have XY updates or show in the available update list :
winget list --upgrade-available --include-unknown
you can use this command to ignore XY updates :
winget pin add --id "CologneCodeCompany.XYplorer"
if you ever need to check if there are updates available for your pinned/ignored apps, you can use this command :
winget list --upgrade-available --include-unknown --include-pinned

admin wrote: ↑18 Jul 2024 11:10 Wow, thanks!

Do you have to work again with each update release?

You are so very welcome! Glad I can contribute a bit. You have written an excellent piece of software!

And no. it's all automated through GitHub workflows...https://github.com/The-Running-Dev/Wing ... es/actions

If you want to incorporate this into your release workflow, let me know, I can help, or simple look at how I have done it. If not, the current process checks for a new versions nightly and publishes it (if one is available, and no other PR already exists for that version).

GreetingsFromPoland wrote: ↑18 Jul 2024 12:24 hi! nice work adding it.

for those of us that use winget for updates but do not want to have XY updates or show in the available update list :
winget list --upgrade-available --include-unknown
you can use this command to ignore XY updates :
winget pin add --id "CologneCodeCompany.XYplorer"
if you ever need to check if there are updates available for your pinned/ignored apps, you can use this command :
winget list --upgrade-available --include-unknown --include-pinned

Welcome! And thank you for providing the info for people new to WinGet. By the way you do not need the quotes:
winget pin add --id CologneCodeCompany.XYplorer

Also, you do not need to do this manually. For full automatic updates, I use this awesome PowerShell project. https://github.com/Romanitho/Winget-AutoUpdate

iryx wrote: ↑31 Jul 2024 18:47 If you want to incorporate this into your release workflow, let me know, I can help, or simple look at how I have done it. If not, the current process checks for a new versions nightly and publishes it (if one is available, and no other PR already exists for that version).

Great! And good enough. I don't think I need to do anything.

admin wrote: ↑01 Aug 2024 09:41

iryx wrote: ↑31 Jul 2024 18:47 If you want to incorporate this into your release workflow, let me know, I can help, or simple look at how I have done it. If not, the current process checks for a new versions nightly and publishes it (if one is available, and no other PR already exists for that version).

Great! And good enough. I don't think I need to do anything.

You do not need to do anything. However, there is one small caveat that you and users should be aware of. Because this auto-publish process works on a cron job nightly, if you do frequent updates to the installer, the hash in the WinGet repo can get mismatched, and then it will refuse to install. For example if today you publish version 1.0, tonight the package gets submitted, it takes a day to approve, but in the meantime you update the installer to new version. Now the WinGet package uses the hash of the old installer, so WinGet will refuse to install (unless you specify --ignore-secruity-hash, which is not the best option. Regardless, this will correct itself the next night after it gets the new version, and pushes the latest package with the latest installer. Sometimes that can take a day or two get in-sync. Just FYI. If you want to avoid this, name each installer with the version, and keep all versions on your web site. Just a suggest.

Okay, thanks. This happens very rarely, so I think it's okay for now.