The path used when releasing binaries is no longer correct, leading to broken releases.
Changes
The file is already at the correct path, so remove the line of code that moves the file. It is the move that was failing during releases.
Made the file executable. Previously it was executable as it had just been built. Now it has been downloaded and needs to have the executable flag set.
Cargo binstall cannot be tested until there is a proper release. Maybe it could be tested by temporarily releasing a valid semantic version that would never be used, testing binstall, then deleting that release. Let me try that. Nope, that won't work. Unfortunately I see no way of testing that other than by making a real release.
Motivation
The path used when releasing binaries is no longer correct, leading to broken releases.
Changes
Tests
I have pushed a beta tag to this PR.
Cargo binstall cannot be tested until there is a proper release. Maybe it could be tested by temporarily releasing a valid semantic version that would never be used, testing binstall, then deleting that release. Let me try that. Nope, that won't work. Unfortunately I see no way of testing that other than by making a real release.