Skip to content

Releasing

Releases live on Natetronn/penates: installers, the in-app update file (latest.json), the AUR tarball and an Arch package (penates-bin-<ver>-1-x86_64.pkg.tar.zst) are attached to each GitHub release. Builds sit in a draft (visible only to the repo’s owners) until you publish them.

  • The repo secret TAURI_SIGNING_PRIVATE_KEY holds the updater key (gh secret list shows it).
  • gh is signed in with access to the repo.
  • For the AUR: an AUR account with your SSH key, and ~/.ssh/config using that key for aur.archlinux.org. Both packages (penates-bin, penates) exist since 0.1.1.
  1. Bump version in the root Cargo.toml (workspace) and pkgver in packaging/arch/PKGBUILD, then run cargo check so Cargo.lock picks up the new version (every --locked build fails otherwise). Move the [Unreleased] notes in CHANGELOG.md under the new version and add its compare link at the bottom. If dependencies changed, regenerate the credits and license texts: python3 scripts/gen-credits.py (CI checks them). Refresh the built-in preset copy: curl -fsSL https://raw.githubusercontent.com/Natetronn/penates-apps/main/catalog.json into crates/penates-core/data/presets.json (keep its _comment), or copy it from a penates-apps checkout. If the manager looks different, regenerate the screenshots in docs/images/ from the real manager: scripts/screenshots.sh (an Arch container with a virtual display; needs docker).
  2. Optional rehearsal: Actions → Release → Run workflow builds and signs every installer without uploading anything.
  3. Commit, then tag and push: git tag v0.2.0 && git push origin v0.2.0.
  4. The Release workflow checks that the tag matches Cargo.toml, builds and signs installers on Linux, Windows and macOS (Apple Silicon and Intel), builds the Arch package from the Linux tarball in an Arch container, and attaches them to a draft release. Nothing is public yet.
  5. When it is green: scripts/publish-release.py v0.2.0 --dry-run, then without --dry-run. It downloads the draft’s files (refusing duplicates or files of another version), writes latest.json, uploads it to the draft, sets the notes from CHANGELOG.md, publishes the release, and updates both AUR packages in packaging/aur/ (penates-bin from the release tarball, penates from the tag’s source).
  6. Commit the updated packaging/aur files here and push: that also rebuilds the website, which describes the latest release (its docs, screenshots and demo come from the release’s source).
  7. AUR: scripts/push-aur.sh clones each package into a temporary folder, copies in packaging/aur/<name>/{PKGBUILD,.SRCINFO}, commits and pushes, then deletes the folder. It needs your AUR key for aur.archlinux.org (in ~/.ssh/config: Host aur aur.archlinux.org with its IdentityFile).

Pre-releases (v0.2.0-rc.1): scripts/publish-release.py v0.2.0-rc.1 --prerelease. They are published as pre-releases, never as “latest”, so installed copies do not update to them, and the AUR is left alone.

A bad draft: delete the draft release and the tag (git push --delete origin v0.2.0 && git tag -d v0.2.0), fix, and tag again.

The desktop app uses Tauri’s updater. It reads https://github.com/Natetronn/penates/releases/latest/download/latest.json, verifies the signature of the download with the public key in src-tauri/tauri.conf.json, installs, and restarts.

Install type Updates
AppImage, .deb, .rpm, Windows installer, macOS .app in the app: Install and restart
AUR (penates-bin, penates), other package managers git pull && makepkg -si in the package’s folder, or an AUR helper (paru -Syu, yay -Syu); the app says so
Tarball, dev builds the app links to the releases page
  • Private key: ~/.tauri/penates.key on the release machine (no password), and the repo secret TAURI_SIGNING_PRIVATE_KEY used by the Release workflow.
  • Public key: plugins.updater.pubkey in src-tauri/tauri.conf.json.
  • Back up ~/.tauri/penates.key. If it is lost, installed copies can never verify another update; a new key means users must reinstall by hand. Never commit it.

python3 scripts/downloads.py prints every release file’s downloads by platform, and the repo’s traffic for the last 14 days. GitHub keeps only running totals, so the Stats workflow appends dated counts to downloads.csv on the stats branch every Monday (or run it by hand: Actions → Stats → Run workflow). latest.json counts update checks, not people. Downloading a whole release adds one to every file, so checks should fetch only the files they need.