The signed executables in dk-exe have compiled versions from dk-exe-pending ... which are different versions. The logic for the next version to pick expects the current version is in the linked list in the server summary.json.
The different versions (succ_asset_version) are due to needing two GitHub releases (one for pending, and one for the signed). It would be better to tag the GitHub release for dk-exe-pending as "-unsigned" so there is no conflict, and the version number can be the same for both listings.
The signed executables in dk-exe have compiled versions from dk-exe-pending ... which are different versions. The logic for the next version to pick expects the current version is in the linked list in the server summary.json.
The different versions (
succ_asset_version) are due to needing two GitHub releases (one for pending, and one for the signed). It would be better to tag the GitHub release for dk-exe-pending as "-unsigned" so there is no conflict, and the version number can be the same for both listings.