Roadmap 0.11, Fixes

FX.340 Studio on macOS can auto-update: publish takes the signed .app.tar.gz as an update-only file

  • Fix
  • Built · in the lab

Found by the 0.10 Mac build (2026-11-16): 0.9 never made a macOS updater file, and Downloads::publish only took update entries for files in the download set, so a Mac copy was always told "no update" (204). The 0.10 Mac build made CadCraft-Studio-0.10-mac.app.tar.gz, signed on the server with the owner's updater key, and two dmg entries (darwin aarch64 + x86_64). Downloads::collectUpdateEntries now takes an entry's .app.tar.gz from handoff/from-mac/<x.y.z>/ (or staged-<x.y.z>), checksum checked, copies it into the release folder and marks the entry update_only (not in the manifest's files, not on /download); updateEntries() accepts such an entry when the file is there at its size; Apache serves .gz without Content-Encoding (AddEncoding is off), so the bytes reach the updater as signed. Releases published before keep their entries as they were. Checked: php -l, test-update-feed 83/0, test-product 616/0, the live 0.8.0 Windows check still 200. Not checked: the path only runs in a real publish (the dry run skips entries); no Mac has installed an update yet.

Verified 2026-11-20 (0.11 close-out): the 0.10.0 release folder is published with updates.json (darwin aarch64 + x86_64). GET /api/v1/updates/darwin/aarch64/0.9.0?edition=dmg -> 200 with version 0.10.0 and a 428-character signature; x86_64 -> 200; from 0.10.0 -> 204. The file URL 302s to cdn.getcadcraft.com and the CDN serves 424,665,008 bytes, the same size as handoff/from-mac/0.10.0 and sha256 2839a2d3... as in updates.json. test-update-feed 83 passed, 0 failed. Only an older Mac installing the update remains: FX.340-HAND.

Add a comment

Community comments

No comments yet

Add detail as we go: how you would use it, files or steps that show the problem, what other programs do. The team reads every comment.

Sign in or create a free account to add a comment.