Open X9VoiD opened 10 months ago
How would you prefer this to be fixed? Can we grab the release names from the git repo itself (ie. submodule), or does this need a GitHub API call on build? Or would you like to just check for both old and new names on compile time?
Can we pull jsons and read from that when building the site? We can probably put a json in master that defines the filenames for the downloads. Something like:
https://raw.githubusercontent.com/OpenTabletDriver/OpenTabletDriver/master/metadata.json
{
"versions": [
"0.5.0.0",
"0.5.0.1",
...
],
"latestReleaseFilenames": {
"windows": "https://github.com/OpenTabletDriver/OpenTabletDriver/releases/download/<version>/opentabletdriver.windows-<version>.<arch>.zip",
"deb": "https://github.com/OpenTabletDriver/OpenTabletDriver/releases/download/<version>/opentabletdriver-<version>.<arch>.deb",
...
}
}
This theoretically solves both needing to update versions manually from this side and this issue.
These are the original filenames for release assets.
In the future we might offer official arm64 releases so renaming the release assets to generic names is not going to be something we're doing when it happens.
This image for example should say and download
opentabletdriver-0.6.4.0-1.x86_64.rpm
Related upstream issue: https://github.com/OpenTabletDriver/OpenTabletDriver/issues/3123