Edit photos by describing the change, on your own GPU. A free, open-source alternative to Nano Banana and ChatGPT image editing: photos stay on your computer, no daily limit. One installer for Windows, Mac and Linux sets up the best open model (Qwen-Image 2.1). MCP server for AI agents.
TypeScript ai-photo-editorcomfyui-alternativegenerative-fillimage-editingimage-generationinpaintinglinuxlocal-aimacosmcpmcp-servernano-banana-alternativeofflinephoto-editorprivacyqwen-imageqwen-image-2-1stable-diffusion-cppvulkanwindows
Releasing Kokon
How to publish a version that installed copies update to, on Windows, macOS and Linux. Every release ships all three from the same code.
How updates work
- Once a day (unless turned off), the app reads
https://github.com/GabrieleLozupone/kokon/releases/latest/download/latest.json. - If its
versionis newer than the app's, a Update to x.y.z pill appears in the top bar. - One click downloads the installer (Windows) or the app archive (Mac) and checks its
signature against the public key in
src-tauri/tauri.conf.json. Then it stops the local service, installs, and restarts Kokon. Settings, gallery and models are kept. - The check needs the repository to be public (it is since 2026-10-11): GitHub serves the release files of a private repo only to signed-in users.
The signing key (do this once)
- The private key lives in
~/.tauri/kokon-updater.key(on Windows%USERPROFILE%\.tauri\kokon-updater.key), and its public half is intauri.conf.json. - Back it up (password manager, encrypted drive). If it's lost, already installed copies can never be updated again: you'd need a new key and every user would have to reinstall by hand.
- Never commit it. It lives outside the repo on purpose.
- Mac: copy it to
~/.tauri/kokon-updater.key(for example over AirDrop, thenchmod 600 ~/.tauri/kokon-updater.key). Both build scripts read it from there, or from theTAURI_SIGNING_PRIVATE_KEYenvironment variable.
Publishing a version
- Bump the version in
src-tauri/tauri.conf.json,Cargo.toml(workspace) andpackage.json, all to the same value. The updater only offers versions higher than the installed one. Also bump the MCP server:cd mcp && npm version <x.y.z> --no-git-tag-version, then both"version"fields inmcp/server.json(npm testinmcp/fails until all match;kokon-mcp --versionreadsmcp/package.json). Update What's new too:WHATS_NEW_VERSIONand the notes insrc/components/WhatsNew.tsx(shown once after the update; with the old version there it never appears). - Windows:
powershell -ExecutionPolicy Bypass -File scripts\build-release.ps1 - Mac:
bash scripts/build-release-mac.sh. Linux: in WSL Ubuntu 22.04 (clone in~/kokon, see linux.md),bash scripts/build-release-linux.sh→.deb,.rpmandupdater-linux-x86_64-{deb,rpm}.json. Then copy each machine'sdist-release/files to the PC so that one folder holds every platform's files. - Write the manifest:
node scripts/release/updater.mjs manifest --notes "What changed, in one or two lines"(latest.jsonmust list Windows, macOS and both Linux packages). Release notes go inmarketing/release-notes-<version>.md, with each installer's SHA-256. - Publish (the tag must be
v+ the version):gh release create v0.9.1 --draft --target master --title "Kokon 0.9.1" --notes-file notes.md \ dist-release/Kokon_0.9.1_x64-setup.exe dist-release/Kokon_0.9.1_aarch64.dmg \ dist-release/Kokon_0.9.1_aarch64.app.tar.gz dist-release/latest.json- What people download:
Kokon_<version>_x64-setup.exeon Windows (Kokon Setup.exein dist-release is an identical copy, not uploaded) and the.dmgon a Mac. - What the updater downloads: the
_x64-setup.exeand the.app.tar.gz, whichlatest.jsonpoints to. - Put the installer's SHA-256 in the notes.
- A release marked pre-release is not "latest", so the updater ignores it.
- Review the draft on GitHub, then press Publish.
- What people download:
- Adding the other platform later (e.g. the Mac build after the Windows one):
- Copy its files and its
updater-<platform>.jsoninto the samedist-release/. - Run the manifest step again.
- Upload with
gh release upload v0.9.1 <files> dist-release/latest.json --clobber.
- Copy its files and its
- Docker image: publishing the release starts
.github/workflows/docker.yml, which buildsdocker/Dockerfileand pushesghcr.io/gabrielelozupone/kokonwith the tags<x.y.z>,<x.y>and (not for a pre-release)latest. Check the run in the Actions tab. To build a tag again:gh workflow run docker.yml -f tag=v<x.y.z>. The first push creates the package as private: once, on GitHub → Packages → kokon → Package settings, set its visibility to Public. - MCP server (after the GitHub release is out):
cd mcp && npm login && npm whoami && npm publish(npm loginfirst: an expired login makesnpm publishfail with a misleading E404 Not Found; it runs the build and tests first), thenmcp-publisher login githubandmcp-publisher publishfrommcp/so the MCP Registry lists the new version. Glama (https://glama.ai/mcp/servers/GabrieleLozupone/kokon): Admin → Repository → Sync Server, then Admin → Dockerfile → Build (the saved spec: buildcd mcp && npm ci && npm run build, CMDmcp-proxy -- node ./mcp/build/kokon-mcp.cjs; no Kokon app needed to list the tools), and on the passed test Create Release with the new version. The release is what Glama grades the tools on.
Testing an update
- Install version A (for example 0.9.0) from its installer.
- Publish version B (0.9.1) as above.
- Open A. The check runs at startup, at most once a day; to force it, use Settings → General → Check now. Then click Update to 0.9.1. Kokon restarts as 0.9.1, and Settings → General shows the new version.