Release v0.3.4: embed Windows manifest (#74)

Diagnosed via PE-header inspection of the v0.3.3 artifact: no embedded
manifest at all (no resource directory in the PE). Recent Windows 11
builds reject naked MSVC binaries with "This version of … uvr.exe is
not compatible with the version of Windows you're running" because the
OS can't determine the binary's supportedOS without a manifest.

Fix: add `embed-manifest` as a Windows-only build-dep and run it from
crates/uvr/build.rs to embed a default manifest (supportedOS = Win 7
through Win 11, asInvoker execution level). Verified locally: macOS
build still passes, Cargo.lock picks up embed-manifest 1.5.0.

Per cadence #69 install-blocking-bug exception: v0.3.3 was unusable
for every Windows user who installed via the released binary.

Verification path: B-Nilson (#74 reporter) builds from cargo source
worked locally — the new artifact will too if my hypothesis holds.
Will ping for confirmation.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: nbafrank

CHANGELOG.md

@@ -7,6 +7,32 @@ release page on GitHub. Issue numbers reference https://github.com/nbafrank/uvr/
 
 Pure tracking section — fixes and small features land here between tags.
 
+## v0.3.4 (2026-05-03)
+
+Hotfix for #74: Windows 11 users running the v0.3.3 release artifact saw
+"This version of … uvr.exe is not compatible with the version of Windows
+you're running." Building from source via cargo worked; the released
+artifact didn't.
+
+Diagnosis: PE-header inspection of the v0.3.3 artifact showed no
+embedded resource directory and no Win32 application manifest at all.
+Recent Windows 11 builds reject naked MSVC binaries — without a
+manifest declaring `supportedOS` GUIDs, the OS treats the exe as
+"compatibility unknown" and refuses to run it. The default Cargo build
+on `windows-latest` (now Win Server 2025 + VS 17.14, linker 14.44)
+doesn't embed a manifest by itself.
+
+### Fixes
+- **Windows binary now embeds a Win32 application manifest (#74)** via
+  the `embed-manifest` build-dep. Manifest declares `supportedOS` GUIDs
+  for Windows 7 through Windows 11 and `asInvoker` execution level.
+  Build-dep is gated under `[target.'cfg(windows)'.build-dependencies]`
+  so non-Windows targets are unaffected.
+
+Per the batched-cadence rule (#69), this tag is allowed under the
+install-blocking-bug exception — every Windows user trying to install
+v0.3.3 currently has a broken binary.
+
 ## v0.3.3 (2026-04-30)
 
 Hotfix for v0.3.2's Linux PPM binaries — the feature was end-to-end

Cargo.lock

@@ -3,7 +3,7 @@ members = ["crates/uvr", "crates/uvr-core"]
 resolver = "2"
 
 [workspace.package]
-version = "0.3.3"
+version = "0.3.4"
 edition = "2021"
 authors = ["uvr contributors"]
 license = "MIT"

Cargo.toml

@@ -34,6 +34,15 @@ semver.workspace = true
 tempfile.workspace = true
 ureq.workspace = true
 
+[target.'cfg(windows)'.build-dependencies]
+# Embed a Win32 application manifest declaring `supportedOS` GUIDs from
+# Windows 7 through Windows 11. Without this, recent Windows 11 builds
+# reject the unmanifested binary at exec time with "This version of …
+# uvr.exe is not compatible with the version of Windows you're running."
+# (See #74 — confirmed via PE-header inspection of the v0.3.3 release
+# artifact: no resource directory, no manifest at all.)
+embed-manifest = "1.4"
+
 [dev-dependencies]
 assert_cmd.workspace = true
 predicates.workspace = true

crates/uvr/Cargo.toml

@@ -0,0 +1,24 @@
+// Embed a Win32 application manifest into the uvr.exe PE so Windows
+// recognises the binary as compatible with Win 7 through Win 11.
+// Without it, naked MSVC binaries built on recent toolchains (the
+// `windows-latest` GH runner currently linker 14.44+) are rejected on
+// some Win 11 builds with "This version of … uvr.exe is not compatible
+// with the version of Windows you're running" — issue #74.
+//
+// `new_manifest("uvr")` produces a manifest declaring supportedOS GUIDs
+// for Vista, 7, 8, 8.1, 10, 11 and asInvoker execution level.
+//
+// This file is a no-op on every non-Windows target; the build-dep is
+// also gated by `[target.'cfg(windows)'.build-dependencies]` so non-
+// Windows builds don't even pull the crate.
+
+#[cfg(windows)]
+fn main() {
+    use embed_manifest::{embed_manifest, new_manifest};
+    embed_manifest(new_manifest("uvr")).expect("unable to embed Win32 manifest");
+}
+
+#[cfg(not(windows))]
+fn main() {
+    // Nothing to do on non-Windows targets.
+}