Skip to content

Distribution: package and publish for Linux (AUR/Flatpak/AppImage), macOS (Homebrew), Windows (winget) #6

Description

@robflowk

Goal

Installable builds for all three platforms through the channels users actually use:

  • Linux: AUR, Flatpak, AppImage
  • macOS: Homebrew (cask)
  • Windows: winget

Plan

Phase 1 — Release pipeline (prerequisite for everything)

  • GitHub Actions workflow using tauri-apps/tauri-action: build on tag push for macOS (universal or arm64+x64), Windows (NSIS), Linux (AppImage + .deb + .rpm — Tauri's bundler produces all three already)
  • Publish artifacts to GitHub Releases with checksums
  • Decide on the Tauri updater plugin (needs a signing keypair) — nice-to-have, not blocking

Phase 2 — Signing (unblocks the package managers)

  • macOS: Developer ID certificate + notarization in CI (without it, Homebrew users get Gatekeeper blocks)
  • Windows: code-signing cert (winget accepts unsigned but flags it; signing strongly preferred)

Phase 3 — Channels

  • AppImage: already produced by Phase 1, just attach to releases
  • AUR: babel-shift-bin PKGBUILD sourcing the release artifacts; optionally babel-shift (source build) later
  • Homebrew: start with a personal tap (robflowk/homebrew-tap) cask pointing at the notarized dmg; homebrew-cask mainline once the project has traction
  • winget: manifest PR to microsoft/winget-pkgs referencing the NSIS installer
  • Flatpak: manifest + Flathub submission (most involved: needs offline-buildable deps; Tauri has documented guidance)

Notes

  • Bundle identifier is already set (com.robinwloka.babelshift in tauri.conf.json) — Flathub app ID should match
  • Version currently 0.1.0; the release workflow should derive from the tag

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions