Desktop Release API

The HummyTummy Desktop app’s installers and updates are served from a server-side release catalog (DesktopRelease). The catalog is a single platform-level global list — every restaurant tenant sees the same published releases. A few endpoints are publicly accessible (download, update query, latest release); publishing a release is restricted to platform operators (SuperAdmin) or CI/CD.

Public endpoints

These endpoints require no authentication (@Public) and are rate-limited (throttled).

Only releases with published: true are visible through the public endpoints. Draft (unpublished) releases are listed only via the SuperAdmin management endpoints.

Get the latest release

GET /api/desktop/releases/latest returns the single newest published release record. If there is no published release it returns 404.

curl https://app.hummytummy.com/api/desktop/releases/latest

{
  "id": "01J...",
  "version": "0.2.6",
  "releaseTag": "v0.2.6",
  "published": true,
  "pubDate": "2026-06-20T15:00:00.000Z",
  "windowsUrl": "https://github.com/.../HummyTummy-POS_0.2.6_x64.msi",
  "windowsSignature": "dW50cnVzdGVkIGNvbW1lbnQ6...",
  "macArmUrl": "https://github.com/.../HummyTummy-POS_0.2.6_aarch64.dmg",
  "macArmSignature": "dW50cnVzdGVkIGNvbW1lbnQ6...",
  "macIntelUrl": "https://github.com/.../HummyTummy-POS_0.2.6_x64.dmg",
  "macIntelSignature": "dW50cnVzdGVkIGNvbW1lbnQ6...",
  "linuxUrl": "https://github.com/.../hummy-tummy-pos_0.2.6_amd64.AppImage",
  "linuxSignature": "dW50cnVzdGVkIGNvbW1lbnQ6...",
  "releaseNotes": "## What's New\n- Feature X\n- Bug fix Y",
  "changelog": null,
  "downloadCount": 134,
  "createdAt": "2026-06-20T14:55:00.000Z",
  "updatedAt": "2026-06-20T15:00:00.000Z"
}

Per-platform package fields

A client picks the URL field that matches the platform it runs on:

If the URL for a given platform is null, that release was not built for that platform.

GET /api/desktop/releases/published returns the same record shape as an array, sorted by pubDate descending (newest first).

The updater endpoint

GET /api/desktop/updates/:platform/:currentVersion

The desktop app uses the Tauri updater to fetch new versions on its own. The flow is fully server-controlled: the app reports the platform it runs on and its current version, and the server returns a signed update manifest if an upgradable release exists.

Valid platform keys: windows-x86_64, darwin-aarch64, darwin-x86_64, linux-x86_64. This endpoint is public and rate-limited to 60 requests/min.

Responses

• Update available → 200 with the manifest below.
• No update / not applicable → the body is null. Tauri treats this as “up to date”. null is returned when:
  • the current version equals or is newer than the latest published release,
  • there is no published release,
  • the requested platform is not present in the latest release (no URL, or unsigned).

curl https://app.hummytummy.com/api/desktop/updates/windows-x86_64/0.2.5

{
  "version": "0.2.7",
  "notes": "## What's New\n- Feature X",
  "pub_date": "2026-06-20T15:00:00.000Z",
  "platforms": {
    "windows-x86_64": {
      "url": "https://github.com/.../HummyTummy-POS_0.2.7_x64.msi",
      "signature": "dW50cnVzdGVkIGNvbW1lbnQ6..."
    },
    "darwin-aarch64": { "url": "...", "signature": "..." },
    "darwin-x86_64":  { "url": "...", "signature": "..." },
    "linux-x86_64":   { "url": "...", "signature": "..." }
  }
}

The platforms object only includes platforms that have both a URL and a valid signature (see the security note below). The notes field is the release’s releaseNotes text, and pub_date is the publication date in ISO format.

Version comparison

The server compares versions as numeric semver: it splits the major.minor.patch parts, strips a leading v prefix, and compares numerically. An update is offered only when the latest published version is strictly greater than the supplied currentVersion; if equal or lower, it returns null.

Signature verification (security)

The Tauri updater installs a binary only if its minisign signature verifies against a pinned public key. The server behaves to preserve that contract:

• If a platform has a URL but no signature (empty/missing), that platform is not added to the manifest — it is treated as not-installable and a warning is logged on the server. A half-populated, unsigned entry is never emitted.
• If a platform has no URL (the release was not built for that platform), it is silently skipped.
• If the requested platform ends up absent from platforms, the endpoint returns null.

This guarantees the auto-updater never receives an unsigned (and therefore unverifiable) binary.

Download counter

POST /api/desktop/releases/:version/download/:platform

Increments the per-release download counter for analytics.

curl -X POST https://app.hummytummy.com/api/desktop/releases/0.2.6/download/windows-x86_64

{ "message": "Download tracked" }

This call is best-effort: if an unknown version is supplied it does not throw, it is just logged on the server.

Publishing a release (operator / CI)

A new release reaches the catalog through one of two routes.

Auth realms

Management endpoints

Example — create a release via CI

curl -X POST https://app.hummytummy.com/api/desktop/ci/releases \
  -H "x-api-key: $DESKTOP_RELEASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "version": "0.2.7",
    "releaseTag": "v0.2.7",
    "releaseNotes": "## What'\''s New\n- ...",
    "windowsUrl": "https://github.com/.../setup.msi",
    "windowsSignature": "dW50cnVzdGVkIGNvbW1lbnQ6...",
    "published": false
  }'

await fetch("https://app.hummytummy.com/api/desktop/ci/releases", {
  method: "POST",
  headers: {
    "x-api-key": process.env.DESKTOP_RELEASE_API_KEY!,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    version: "0.2.7",
    releaseTag: "v0.2.7",
    releaseNotes: "## What's New\n- ...",
    windowsUrl: "https://github.com/.../setup.msi",
    windowsSignature: "dW50cnVzdGVkIGNvbW1lbnQ6...",
    published: false,
  }),
});

Building from source

To build the desktop app from source (the Tauri CLI ships with npm):

npm install
npm run tauri:dev    # run in development mode
npm run tauri:build  # produce a production bundle

Development requires Rust 1.70+ and Node.js 18+; on Linux you also need libdbus-1-dev and pkg-config (for Bluetooth printer support).

Operator screens

End users do not call these endpoints directly — the desktop app does. Operators install and update the app through the in-app experience:

• Install & download (operator guide): help.hummytummy.com
• Auto-update (operator guide): help.hummytummy.com