v0.12.1

🩹 The cask release that couldn't read its own version

v0.12.0 shipped Homebrew cask releases. It just couldn't finish one — because the pack gate asked Tauri for a DMG and then went looking for an app bundle Tauri had never been told to keep. This release makes that whole path actually work.

🔨 The pack gate now builds what it inspects

The version gate's whole job is paranoia: before anything is tagged, notarized or pushed, it opens the artifact you just built and asks it what version it thinks it is. That answer lives in the .app's Info.plist — but the build only requested --bundles dmg, so the .app was a leftover from whatever happened to be on disk before, or nothing at all.

The build now asks for --bundles app,dmg. The .app supplies the embedded version the gate reads; the DMG is still the one artifact that ships. Same gate, same guarantees — except now it's inspecting the build in front of it instead of an artifact that may never have existed. 🔍

And because a fixture that quietly does the right thing is how a contradiction like this hides for a whole release cycle, the test builder now honors the bundle formats it was actually handed. Ask it for dmg and you get a dmg — nothing more. The bug can't come back wearing a green test suite. ✅

📦 Getting it

bun update @kvnwolf/dobby

No config changes, no migration, nothing to re-declare. If your project has a release.type: "homebrew-cask" target, this is the version where bunx dobby release gets past the pack gate. Everyone else is unaffected — the npm release path never touched this code.