Releasing
One GitHub Release builds the installers and the container image.
What a release publishes
| What | Where |
|---|---|
Windows: Luna-Setup-<version>.exe and a portable zip | Release assets |
macOS (unsigned): .dmg and .zip for Apple silicon and Intel | Release assets |
Linux: .AppImage for x64 and arm64 | Release assets |
Android app Luna-<version>-android.apk | Release assets |
| iOS simulator build | Release assets |
Server + web UI Luna-<version>-server.zip | Release assets |
SHA256SUMS-<version>.txt and Luna-<version>.intoto.jsonl provenance | Release assets |
| Container image | ghcr.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
Bump the version
Edit "version" in interfaces/desktop/package.json. It names every file and image tag.
Merge to main
With npm run test:smoke, npm run build and the container check green on the PR.
Publish the release
gh release create v0.3.0 --target main --title "Luna 0.3.0" --notes-file notes.mdThe workflows attach the apps and push the image when they finish.
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.
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 imageSigning notes
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.