We tagged Desktop 0.1.6, Codemagic published a signed macOS build, and Windows Check for updates died.
Tauri 2 looks up windows-x86_64-nsis first, then windows-x86_64. A darwin-only channel latest.json has neither:
None of the fallback platforms ["windows-x86_64-nsis", "windows-x86_64"] were found
The tempting fix — copy yesterday's Windows bits into today's version field — would have been worse. Existing Windows installs would loop on a same-version "update".
Same-version merge, not a franken-manifest
Merge platforms only when the version matches. Alias windows-x86_64 to windows-x86_64-nsis. Keep a versioned desktop/stable/{version}/latest.json so the second OS can catch up even if the channel file is left alone. Refuse to replace the channel when a new version would drop Windows or darwin.
desktop_cdn_status on meronq-local is the probe we wished we had before the first Windows user hit Check for updates. The website /download/ is static aliases into R2 — a Desktop version bump does not need a Pages rebuild.
Windows-first when you can. If Codemagic already wrote darwin-only, a Windows pnpm desktop:release of the same version restores the missing platforms.
What else is in the tag
The sidecar now records response_bytes the same way MCP tools do — 0.1.5 capped MCP answers; Desktop access rows still had no size. skill_propose / skill_apply sit next to JSON Project Skills (custom kind: command stays locked in v0). The old social publishing module is now deploy: Codemagic plus Discord / Telegram / dev.to / LinkedIn, on meronq-local only.
This is a Desktop release, not a sprint close. Sprint 24's UI shell did not ship.
Windows and macOS both update in place.
Read the full post on meronq.pages.dev · Source on GitHub
Top comments (0)