TUKO/TUKO for Windows/Shipping updates
TUKO Desktop · release process

Shipping updates:
one build, one folder, every till current.

TUKO for Windows updates itself from a static feed — a few files on any HTTPS host. This page is how a release gets from a build machine to every till: what the build produces, what the feed serves, what installed apps do, and how signing fits in.

v0.3.0 · Windows 10/11, 64-bit · ~83 MB · Portable build

What's new in 0.3.0

Version 0.3.0 ships the free-first 1.3.0 app bundle — the whole TUKO workspace is now free (fair use: 3 workspaces, 1 GB storage per account). The paywall is gone, the Billing screen is informational only (plan, invoices, usage — nothing to buy), and Cash Flow Foresight and Revenue Recovery are included without a plan gate.

The desktop shell itself is unchanged — this is a bundle-content release, so auto-update delivers it with no reinstall and no re-login. The macOS 0.3.0 dmg ships with the signed Mac build; until it lands on the feed, latest-mac.yml keeps serving 0.2.0 and Windows machines update to 0.3.0 normally.

The update feed is a folder, not a server

The app's update configuration points at a static feed root — https://downloads.tukohq.com/desktop/ — declared in desktop/electron-builder.yml under publish.url. There is no update server to run, patch, or keep awake: the feed is three or four files on any static HTTPS host. A Netlify site, Cloudflare R2, or S3 behind a CDN all work the same.

Public download links don't hit the feed host directly: tukohq.com/download/desktop/* is a Netlify proxy onto the feed, so the download buttons on /desktop/ stay on-origin — the browser shows a clean filename and the page reads latest.yml with no CORS setup on the feed host. Those buttons resolve the newest version from latest.yml at load time, so publishing a release requires no change to the marketing pages.

Two ways to publish under the same URL: a file committed to landing/download/desktop/ is served straight from the site deploy (real files win over the proxy — this is how the first release ships before the feed exists), and anything not committed falls through the proxy to the feed host. Keep latest.yml out of the repo so the resolver always sees the feed's newest release once it is live.

At the feed root, two kinds of files:

latest.ymlThe Windows manifest — the newest version number, the installer filename, and its checksum. This is the only file a Windows app reads to decide whether to update.
latest-mac.ymlThe macOS manifest — same role as latest.yml, generated by the Mac build. Mac download buttons resolve it for the newest version too.
TUKO-Setup-*.exeThe Windows NSIS installer — the full install that auto-updates itself from then on.
TUKO-*.dmgThe Mac installer — open, drag to Applications. Users download this one.
TUKO-*.zipThe Mac auto-update payload — Squirrel.Mac installs updates from the zip, never the dmg. Both ship to the feed; the zip is for the updater.
TUKO-Portable-*.exeThe Windows portable build — runs without installing, for evaluation or one-off machines. It does not auto-update; replace the file when a release ships.

How a release ships

From a clean checkout on a Windows machine, release day is three steps.

1 · Build

npm --prefix desktop run dist compiles the shell, stages the same web export the Netlify app serves, and produces release/*.exe plus latest.yml — signed, if a code-signing cert is configured.

2 · Publish

Upload latest.yml and the installer files to the feed root on your static host. An atomic swap on the host means every till sees the new release at the same moment. Keep the previous installer in the folder — it's the version pinned in the page markup until the resolver upgrades it. Until the feed exists, copy release/*.exe into landing/download/desktop/ and the same public links work off the site deploy.

3 · Done — tills do the rest

Every installed app finds the new latest.yml on its next launch or hourly check, downloads in the background, and installs on quit. No remote sessions, no USB sticks.

The build, verbatim

Run from the repository root — the desktop package compiles itself and pulls in the web export automatically:

# produces desktop/release/*.exe + latest.yml npm --prefix desktop run dist

For a signed build, set the code-signing certificate in the environment first — electron-builder picks it up automatically:

# PowerShell — sign this build with the company cert $env:CSC_LINK = "C:\certs\tuko-codesign.pfx" $env:CSC_KEY_PASSWORD = "…" npm --prefix desktop run dist:win

The macOS build runs on a Mac (signing and notarization are macOS-only):

# macOS — signed + notarized universal build (dmg + zip + latest-mac.yml) # Developer ID Application cert in the login keychain, then: export APPLE_ID="[email protected]" export APPLE_APP_SPECIFIC_PASSWORD="xxxx-xxxx-xxxx-xxxx" export APPLE_TEAM_ID="ABCDE12345" npm --prefix desktop run dist:mac

Unsigned Mac builds still produce a .dmg, but Gatekeeper warns and auto-update cannot install — Squirrel.Mac requires a Developer ID signature. Ship unsigned builds only for evaluation, or set TUKO_DISABLE_AUTO_UPDATE=1 on them.

What installed apps do

Updates are deliberately boring — they land between sessions, never mid-sale.

On every till

  • The app checks the feed on launch and about once an hour while running.
  • A new version downloads in the background — the register keeps working at full speed.
  • The update installs when the app quits. Opening it again is the new version.
  • Queued offline sales and clock-ins are untouched — they live outside the update.

What can go wrong — and doesn't

  • Offline during a check? The check just fails quietly; the app retries at the next interval.
  • Download interrupted? It resumes — an update never applies half-installed.
  • Portable build? It doesn't auto-update — replace the exe with the new one when a release ships.

Signing — and the SmartScreen warning

Unsigned builds work fine; they just earn a reputation check on first install.

Unsigned today

  • Windows SmartScreen flags new or uncommon installers: "Windows protected your PC".
  • It's a reputation check, not a virus verdict — More info → Run anyway proceeds.
  • The warning fades as the signed release builds reputation and as machines install it.

Signed builds

  • Set CSC_LINK and CSC_KEY_PASSWORD to the code-signing certificate before run dist — both installer and app binaries get signed in the same build.
  • Signed, reputably-distributed builds pass SmartScreen cleanly. An EV certificate or Azure Trusted Signing earns that reputation instantly; a standard OV cert builds it over installs.
  • Only install TUKO from tukohq.com — a signed build is only as trustworthy as where you got it.

Rolling back a bad release

Updates only move forward: publishing an older latest.yml does not downgrade machines that already took the new build — they simply see "no newer version" and stay put. To retract a bad release, build from the last good commit, bump the version number, and publish it as a normal update. Every till picks it up on its next check and the rollout is a rollback.

This is why releases ship with a version bump and a changelog entry rather than re-uploading over the same version — the feed's contract is monotonic.

Release questions, answered

Does the update feed need a server?

No — the feed is plain static files over HTTPS. latest.yml plus the installer files sit at the feed root on any static host: a Netlify site, Cloudflare R2, or S3 behind a CDN. There is no update server to run.

What happens if a PC is offline or off during an update?

Nothing breaks. The app checks again on its next launch and its next hourly check — the update simply lands later. A partially downloaded update resumes; it never applies half-installed.

Can a till stay on an older version?

Installed builds update automatically — that is what keeps every till on the same current build. The portable exe does not auto-update; replace it with the new file when a release ships.

How do you roll back a bad release?

Updates only move forward — publishing an older latest.yml does not downgrade installed PCs. To retract a bad release, build from the last good commit, bump the version number, and publish that as a normal update; every till picks it up on its next check.