v1.0.5 has no macOS ARM64 release asset; VS Code updater reports success after HTTP 404

[tarrific]

Summary

The VS Code Parallels Desktop extension cannot update Parallels DevOps on an Apple-silicon Mac from v1.0.4 to v1.0.5. The required release archive returns HTTP 404, but the extension subsequently reports that the service was installed successfully.

Environment

• macOS on Apple Silicon (darwin-arm64)
• Parallels Desktop VS Code extension 1.5.11
• Installed prldevops: 1.0.4, stable channel
• Attempted update: v1.0.5

Reproduction

1. Open the Parallels Desktop VS Code extension on an Apple-silicon Mac.
2. Let it detect v1.0.5 as the latest Parallels DevOps version.
3. Select the extension's install/update action.

Actual result

The extension's output contains:

Installing prldevops v1.0.5 for darwin-arm64
Downloading release v1.0.5
Downloading prldevops release from GitHub Releases
Failed to download prldevops release from GitHub Releases (HTTP status: 404)
install exited with code 1
DevOps Service installed successfully

The v1.0.5 release does not provide the required macOS ARM64 archive (the installer attempts the matching darwin-arm64 release URL), so this is reproducible outside VS Code as well. The current installer script constructs the same download URL.

Expected result

Either:

1. publish a signed macOS ARM64 archive for v1.0.5; or
2. do not advertise v1.0.5 as installable on macOS ARM64 until that asset exists.

Also, the extension should propagate the non-zero installer exit status and show installation failure rather than DevOps Service installed successfully.

Impact

Apple-silicon users cannot update beyond v1.0.4 using the supported VS Code or installer workflow.

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template!

[cjlapao]

@tarrific both issues have been fixed, the binaries have been added and in future the release cycle will fail if any of the binaries have failed to be produced. thanks for raising this.
We will be looking into the 3rd issue in the other repo, why the VSCode extension does not raise an error