Presenter's voice engine now installs from GitHub, built and signed in the open

Presenter 1.9.3 changes where the action gets its voice engine. It installs bisque-voice 0.1.38 now, and it downloads it from GitHub. That release is built, signed and attested in the open, and your workflows need no edits to pick it up.

The version constant in install-bisque-voice.ts moves from 0.1.35 to 0.1.38. That one constant decides which engine the action installs, so every run after the upgrade uses the new build.

Why does this matter to you? The engine runs on your build machines. The maintainers call 0.1.38 the first release built, signed and attested in the open, in the public bisque-voice repository. The binary you run now comes from a build you can inspect.

In the same file, the download URL changes. The tarball used to come from download dot bisque dot today. Now it comes from the GitHub Releases page of the bisque-voice repository, for the same version and the same platform name.

https://download.bisque.today/bisque-voice/v${VERSION}/bisque-voice-${triple}.tar.gz

https://github.com/bisque-cloud/bisque-voice/releases/download/v${VERSION}/bisque-voice-${triple}.tar.gz

The installer pins a SHA-256 checksum for each platform's tarball. The release notes say every one of them is updated to match 0.1.38, on Mac, Linux and Windows. Nothing for you to copy, because the values ship inside the action.

The one thing that can break is the network path. The engine used to come from download dot bisque dot today. It now comes from github dot com. If your runners sit behind an allow list for outbound traffic, add GitHub before you upgrade, or the engine download will be blocked.

Upgrading is a version bump. The change is confined to the installer, so there is nothing to migrate. Point your workflow at presenter v1.9.3 and the new engine installs on the next run. The one reason to hold off is a runner that cannot reach GitHub yet. Otherwise, the voice engine now comes from a build made in the open.