Releasing

One GitHub Release builds the installers and the container image.

What a release publishes

WhatWhere
Windows: Luna-Setup-<version>.exe and a portable zipRelease assets
macOS (unsigned): .dmg and .zip for Apple silicon and IntelRelease assets
Linux: .AppImage for x64 and arm64Release assets
Android app Luna-<version>-android.apkRelease assets
iOS simulator buildRelease assets
Server + web UI Luna-<version>-server.zipRelease assets
SHA256SUMS-<version>.txt and Luna-<version>.intoto.jsonl provenanceRelease assets
Container imageghcr.io/sehastrajit-s/luna:<version> and :latest

Workflows: .github/workflows/build-release.yml (apps) and .github/workflows/docker.yml(image; it also smoke-tests the image on every pull request).

Cutting a release

1

Bump the version

Edit "version" in interfaces/desktop/package.json. It names every file and image tag.

2

Merge to main

With npm run test:smoke, npm run build and the container check green on the PR.

3

Publish the release

terminal
gh release create v0.3.0 --target main --title "Luna 0.3.0" --notes-file notes.md

The workflows attach the apps and push the image when they finish.

4

First release only

Make the container package public: repo → Packages → luna → Package settings → Change visibility → Public.

Building locally

All build output goes under dist/<target>/ and is never committed.

terminal
npm run build:desktop    # dist/desktop/Luna-Setup-<version>.exe
npm run build:mobile     # syncs the web build into interfaces/mobile (then Android Studio / Xcode)
docker build -t luna .   # the container image

Signing notes

📌
Unsigned builds

The Windows installer isn't code-signed, so SmartScreen warns on first run ("More info → Run anyway"). The Android APK is debug-signed for sideloading, and the iOS build runs in the simulator only. Store releases need signing certificates added to the workflow.