You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I'm trying to add zsync updates to the Cemu appimage, but I ran into an issue that I get 404 erros when testing with appimageupdatetool.
The issue ended up being that in Cemu, they have two release types, one is latest which is rarely updated (and last time it was used was before they had an appimage) and the other is a pre-release where the release name is the version of cemu, so it is constantly changing.
Yes, it is recommended that released versions update to released versions, and test versions update to test versions. Think of it as 2 different "update channels".
It can be done, albeit a bit differently than what you describe:
If I remember correctly, in GitHub, "latest" always points to the most recent release of a project, which is not a prerelease version. This means that if a project has both stable and prerelease versions, the "latest" tag will point to the most recent stable version, ensuring that users are directed to a version that is considered stable and ready for production use. If you want to access prerelease versions, you would need to look for specific tags or branches that indicate those versions.
So you could use "latest" to refer to the latest v... whereas you could publish e.g., a "testing" tag under which you'd publish the frequently changed testing version. This tag needs to be flagged as "prerelease" so that GitHub doesn't consider it when calculating "latest".
Hello, I'm trying to add zsync updates to the Cemu appimage, but I ran into an issue that I get 404 erros when testing with appimageupdatetool.
The issue ended up being that in Cemu, they have two release types, one is latest which is rarely updated (and last time it was used was before they had an appimage) and the other is a pre-release where the
release name
is the version of cemu, so it is constantly changing.This mentions to use wildcard for the version in the name of the file so I tested the same trick but on the other field by using
"gh-releases-zsync|$GITHUB_REPOSITORY_OWNER|Cemu|v*|Cemu-*$ARCH.AppImage.zsync"
but it did not work, it still can't find the url.The text was updated successfully, but these errors were encountered: