Repository navigation
how does the "Update Link" field work? #56
Replies: 2 comments 5 replies
|
|
i saw that but i was confused about how exactly it determines which release asset is the correct one from the github repo url alone. though after digging around some more i eventually found my answer in this function |
|
Currently there is no release channel filter implemented, it fetches first available release, this includes pre-releases. That's why #22 is open. I assumed it matters little, since github API supports only two release channels: pre-release and latest. |
|
I discovered this app a week ago and it's great. I was going to ask the same question as the OP. I also come from Gear Lever and I like this app a little more. How does it manage updates? It would be nice to have a small wiki or guide on how to do it, since Gear Lever was a little easier for my taste. In AppManager, if I put, for example: https://github.com/toeverything/AFFiNE/releases it automatically picks the canary version, and I don't want that. I want it to update the stable version, for example. How would I do that? Thanks for creating this. |
|
There is (i) icon near update field that briefly explains how update links work. Basically just past repo url, that's it. Since v3.4.0 you can also define updates channel. Currently GitHub has only two: latest and pre-release. In your case not to have canary updates you should not enable pre-release which by default is disabled. Let me know if it does not work |
|
Some projects ship multiple x64 appimages per release. |
|
Please report upstream to include .zsync update info. |
Uh oh!
There was an error while loading. Please reload this page.
in gear lever there's a separate repo URL & file name field:
but app manager just an "Update Link" field:
does it automatically detect the correct release file name based on your CPU architecture or something? maybe the 💡 icon could be updated with more info about how this works
All reactions