Right now the download page has logic that pulls from the current NPM version on the web app for deciding what link the download link is for desktop. This is not quite accurate since we often bump version earlier than we cut a desktop release. can we do something like parse the "latest" logic in github for finding the link?
We do something similar in the src-tauri download logic, could we do it on the download page too? You can ignore all the signature checking stuff, just focus on getting the latest version that's released and crafting the correct download links for each desktop OS version.
Right now the download page has logic that pulls from the current NPM version on the web app for deciding what link the download link is for desktop. This is not quite accurate since we often bump version earlier than we cut a desktop release. can we do something like parse the "latest" logic in github for finding the link?
We do something similar in the src-tauri download logic, could we do it on the download page too? You can ignore all the signature checking stuff, just focus on getting the latest version that's released and crafting the correct download links for each desktop OS version.