build the app, and ship it on Linux and Windows as well as macOS

The client itself: the sync engine and mirror, the Gmail and IMAP providers,
the screener, the three boxes and two piles, compose and send, the sanitiser
and tracker stripping, contacts, clips, backup, notifications and the guide.

The pipeline that ships it. Three runners now build in parallel and the
publish gate wants all four platform keys in latest.json before a release
leaves draft. Linux gets two more packages Tauri does not build: a flatpak
repackaged from the deb against GNOME 48, and a Nix package that relinks the
deb against nixpkgs so it runs as a native Wayland client rather than through
Xwayland. CI runs the Rust suite on all three desktops rather than on Linux
alone, and rebuilds the flatpak manifest on every push to main.

Two things that were only ever exercised on macOS and were wrong everywhere
else. The menu bar was built by adjusting the submenus macOS is given, so on
a platform whose default menu has no File or View the new File menu landed
after Edit, Check for Updates landed nowhere, and the three places and the
reading pane had no menu at all. The deb declared libwebkit2gtk-4.1-0 and
libgtk-3-0 twice, because tauri.conf.json named the dependencies Tauri
already emits.

The updater key exists now, so releases can sign their artifacts.
This commit is contained in:
pj committed 2026-09-06 12:15:30 +05:30
1 parent 088ec9c6e4
commit eb59cb5f8d
423 files changed
+93217 -251

No files matched your search

+107 -1
View File
@@ -50,8 +50,20 @@ jobs:
- run: node scripts/docs-check.mjs
# Every desktop the release ships to, because the parts of this crate that differ by platform are
# the parts nobody runs by hand: the UserNotifications bridge on macOS, the D-Bus one everywhere
# else, the machine id the refresh tokens are sealed against. A break in one of those used to
# surface at release time on a runner nobody was watching.
rust:
runs-on: ubuntu-22.04
strategy:
fail-fast: false
matrix:
include:
# Ubuntu 22.04 is the glibc baseline the release builds on, so it is what CI tests on.
- os: ubuntu-22.04
- os: macos-26
- os: windows-latest
runs-on: ${{ matrix.os }}
defaults:
run:
working-directory: rust/margin-mail
@@ -61,6 +73,7 @@ jobs:
path: rust/margin-mail
- name: Install Linux dependencies
if: runner.os == 'Linux'
run: |
sudo apt-get update
sudo apt-get install -y \
@@ -79,14 +92,107 @@ jobs:
- uses: swatinem/rust-cache@v2
with:
workspaces: rust/margin-mail/src-tauri -> target
key: ${{ matrix.os }}
# tauri_build::build() wants a frontendDist that exists, and build.rs wants credentials to
# embed. The example file is what a fresh clone compiles against, so that is what CI uses.
- name: Stub the build inputs
shell: bash
run: |
mkdir -p dist && touch dist/index.html
cp google-credentials.example.json google-credentials.json
# The gate docs/release.md names is the test suites, and that is all this enforces. `cargo fmt
# --check` and `cargo clippy -D warnings` both fail on the tree as it stands; adopting either
# is a cleanup pass to decide on separately, not something to bolt onto CI first.
- name: Test
working-directory: rust/margin-mail/src-tauri
run: cargo test
# The flake at whatever release nix/release.json pins. A broken flake, or a deb that no longer
# patches against current nixpkgs, shows up here rather than at the next release. Before the
# first release there is nothing pinned and nothing to build.
nix:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v7
- id: pin
run: echo "version=$(jq -r '.version // ""' nix/release.json)" >> "$GITHUB_OUTPUT"
- uses: cachix/install-nix-action@v31
if: steps.pin.outputs.version != ''
# --impure with the environment variable because the licence is FSL rather than MIT, so
# nixpkgs treats the package as unfree and refuses to build it otherwise.
- if: steps.pin.outputs.version != ''
run: NIXPKGS_ALLOW_UNFREE=1 nix build --impure .#margin-mail --print-build-logs
- if: steps.pin.outputs.version == ''
run: echo "nix/release.json pins no release yet, so there is nothing to build."
# The flatpak manifest is hand-written rather than produced by Tauri, so nothing else would catch
# a runtime that stopped carrying webkit2gtk-4.1 or a permission the app needs and does not ask
# for. The release job repackages the published deb; this one builds the same manifest against a
# deb built here, which is the only difference between them.
#
# On main rather than on every pull request: it is a full release-mode build plus a runtime
# download, the manifest changes about once a year, and a break in it is worth finding within the
# day rather than within the minute.
flatpak:
if: github.event_name == 'push'
runs-on: ubuntu-22.04
defaults:
run:
working-directory: rust/margin-mail
steps:
- uses: actions/checkout@v7
with:
path: rust/margin-mail
- uses: actions/checkout@v7
with:
repository: priyanshujain/margin
path: python/margin
- name: Install Linux dependencies
run: |
sudo apt-get update
sudo apt-get install -y \
libwebkit2gtk-4.1-dev \
libgtk-3-dev \
libayatana-appindicator3-dev \
librsvg2-dev \
patchelf \
libxdo-dev \
libssl-dev \
build-essential \
flatpak \
flatpak-builder
- uses: actions/setup-node@v6
with:
node-version: 26
- uses: pnpm/action-setup@v6
with:
version: 10
- name: Install Rust
uses: dtolnay/rust-toolchain@stable
- uses: swatinem/rust-cache@v2
with:
workspaces: rust/margin-mail/src-tauri -> target
key: flatpak
- run: pnpm install --frozen-lockfile
- run: cp google-credentials.example.json google-credentials.json
- run: pnpm tauri build --bundles deb
- name: Build the flatpak
run: |
mv src-tauri/target/release/bundle/deb/*.deb flatpak/margin-mail.deb
flatpak/build.sh
+148 -4
View File
@@ -44,6 +44,12 @@ jobs:
jq --arg v "$VERSION" '.version = $v' src-tauri/tauri.conf.json > "$tmp" && mv "$tmp" src-tauri/tauri.conf.json
jq --arg v "$VERSION" '.version = $v' package.json > "$tmp" && mv "$tmp" package.json
sed -i "0,/^version = \".*\"/s//version = \"$VERSION\"/" src-tauri/Cargo.toml
# Cargo.lock records margin-mail's own version, so bumping only Cargo.toml leaves the lock
# a release behind and the next build rewrites it under whoever checked it out.
awk -v v="$VERSION" '
/^name = "margin-mail"$/ { print; getline; sub(/^version = ".*"/, "version = \"" v "\""); print; next }
{ print }
' src-tauri/Cargo.lock > "$tmp" && mv "$tmp" src-tauri/Cargo.lock
- name: Commit and tag
env:
@@ -51,7 +57,7 @@ jobs:
run: |
git config user.name "github-actions[bot]"
git config user.email "github-actions[bot]@users.noreply.github.com"
git add src-tauri/tauri.conf.json package.json src-tauri/Cargo.toml
git add src-tauri/tauri.conf.json package.json src-tauri/Cargo.toml src-tauri/Cargo.lock
git commit -m "chore(release): $TAG"
for attempt in 1 2 3 4 5; do
git fetch origin main
@@ -93,6 +99,9 @@ jobs:
- os: ubuntu-22.04
args: "--config src-tauri/tauri.release.conf.json"
rust-targets: ""
- os: windows-latest
args: "--config src-tauri/tauri.release.conf.json"
rust-targets: ""
runs-on: ${{ matrix.os }}
defaults:
run:
@@ -109,7 +118,7 @@ jobs:
path: python/margin
- name: Install Linux dependencies
if: startsWith(matrix.os, 'ubuntu')
if: runner.os == 'Linux'
run: |
sudo apt-get update
sudo apt-get install -y \
@@ -141,6 +150,7 @@ jobs:
- uses: swatinem/rust-cache@v2
with:
workspaces: rust/margin-mail/src-tauri -> target
key: ${{ matrix.os }}
- name: Install frontend dependencies
run: pnpm install --frozen-lockfile
@@ -160,6 +170,42 @@ jobs:
echo "::warning::GOOGLE_CREDENTIALS secret not set, embedding placeholder credentials; this build cannot connect to Gmail."
fi
# macOS shows no notifications from a bundle that is not signed, so tauri.conf.json ad-hoc
# signs at minimum; a Developer ID from the secrets replaces that, and the App Store Connect
# key notarizes on top. Only what is present is exported, because Tauri takes an empty
# APPLE_SIGNING_IDENTITY for an identity and fails the signing step on it.
- name: Provision Apple signing
if: runner.os == 'macOS'
shell: bash
env:
APPLE_CERTIFICATE: ${{ secrets.APPLE_CERTIFICATE }}
APPLE_CERTIFICATE_PASSWORD: ${{ secrets.APPLE_CERTIFICATE_PASSWORD }}
APPLE_SIGNING_IDENTITY: ${{ secrets.APPLE_SIGNING_IDENTITY }}
APPLE_TEAM_ID: ${{ secrets.APPLE_TEAM_ID }}
APPLE_API_ISSUER: ${{ secrets.APPLE_API_ISSUER }}
APPLE_API_KEY: ${{ secrets.APPLE_API_KEY }}
APPLE_API_KEY_P8: ${{ secrets.APPLE_API_KEY_P8 }}
run: |
if [ -z "$APPLE_CERTIFICATE" ] || [ -z "$APPLE_SIGNING_IDENTITY" ]; then
echo "::warning::APPLE_CERTIFICATE or APPLE_SIGNING_IDENTITY not set; the macOS bundle will be ad-hoc signed and not notarized."
exit 0
fi
for name in APPLE_CERTIFICATE APPLE_CERTIFICATE_PASSWORD APPLE_SIGNING_IDENTITY APPLE_TEAM_ID; do
{ echo "$name<<MARGIN_EOF"; printf '%s\n' "${!name}"; echo "MARGIN_EOF"; } >> "$GITHUB_ENV"
done
echo "Signing as $APPLE_SIGNING_IDENTITY"
if [ -n "$APPLE_API_KEY_P8" ] && [ -n "$APPLE_API_KEY" ] && [ -n "$APPLE_API_ISSUER" ]; then
printf '%s' "$APPLE_API_KEY_P8" > "$RUNNER_TEMP/AuthKey.p8"
{
echo "APPLE_API_KEY=$APPLE_API_KEY"
echo "APPLE_API_ISSUER=$APPLE_API_ISSUER"
echo "APPLE_API_KEY_PATH=$RUNNER_TEMP/AuthKey.p8"
} >> "$GITHUB_ENV"
echo "Notarizing with App Store Connect key $APPLE_API_KEY"
else
echo "::warning::APPLE_API_KEY, APPLE_API_ISSUER or APPLE_API_KEY_P8 not set; the macOS bundle will be signed and not notarized."
fi
- name: Build and upload
uses: tauri-apps/tauri-action@v0
with:
@@ -171,8 +217,45 @@ jobs:
TAURI_SIGNING_PRIVATE_KEY: ${{ secrets.TAURI_SIGNING_PRIVATE_KEY }}
TAURI_SIGNING_PRIVATE_KEY_PASSWORD: ${{ secrets.TAURI_SIGNING_PRIVATE_KEY_PASSWORD }}
publish:
- name: Verify the bundle is signed and notarized
if: runner.os == 'macOS' && env.APPLE_API_KEY_PATH != ''
run: |
app="src-tauri/target/universal-apple-darwin/release/bundle/macos/Margin Mail.app"
codesign --verify --deep --strict --verbose=2 "$app"
# Gatekeeper only says "accepted" once the notarization ticket is stapled to the bundle,
# so this is the check that somebody double-clicking the dmg will actually get past.
spctl --assess --type execute --verbose=4 "$app"
xcrun stapler validate "$app"
# The flatpak is not a Tauri bundle target, so it is built here from the deb the Linux job just
# published and uploaded to the same draft release. Before publish, so a release never goes out
# with the Linux artifacts half there.
flatpak:
needs: [prepare, build]
runs-on: ubuntu-22.04
steps:
- uses: actions/checkout@v7
with:
ref: ${{ needs.prepare.outputs.tag }}
- run: |
sudo apt-get update
sudo apt-get install -y flatpak flatpak-builder
- name: Build the flatpak from the published deb
env:
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
REPO: ${{ github.repository }}
TAG: ${{ needs.prepare.outputs.tag }}
VERSION: ${{ needs.prepare.outputs.version }}
run: |
gh release download "$TAG" --repo "$REPO" \
--pattern "Margin.Mail_${VERSION}_amd64.deb" --output flatpak/margin-mail.deb
flatpak/build.sh "$PWD/Margin.Mail_${VERSION}_amd64.flatpak"
gh release upload "$TAG" --repo "$REPO" "Margin.Mail_${VERSION}_amd64.flatpak" --clobber
publish:
needs: [prepare, build, flatpak]
runs-on: ubuntu-latest
steps:
- name: Verify manifest is complete, then publish
@@ -184,10 +267,71 @@ jobs:
gh release download "$TAG" --repo "$REPO" --pattern latest.json --output latest.json --clobber
echo "Platforms in latest.json:"
jq '.platforms | keys' latest.json
for key in darwin-aarch64 darwin-x86_64 linux-x86_64; do
for key in darwin-aarch64 darwin-x86_64 linux-x86_64 windows-x86_64; do
if ! jq -e ".platforms[\"$key\"].url" latest.json > /dev/null; then
echo "::error::latest.json is missing platform '$key', refusing to publish a partial update manifest. Re-run the release."
exit 1
fi
done
gh release edit "$TAG" --repo "$REPO" --draft=false --latest
# Nix is the other Linux package. The AppImage carries Ubuntu's GTK stack, which cannot talk to a
# modern Wayland compositor and silently falls back to Xwayland; the Nix package relinks the
# published deb against nixpkgs' webkit2gtk and runs as a native Wayland client. Runs after
# publish so the flake can only ever point at a release that survived the manifest check.
nix:
needs: [prepare, publish]
runs-on: ubuntu-latest
steps:
# main rather than the tag: the pin lands on main, and the tag was cut before the artifact
# it needs the hash of existed.
- uses: actions/checkout@v7
with:
ref: main
- name: Pin the flake to this release
env:
VERSION: ${{ needs.prepare.outputs.version }}
REPO: ${{ github.repository }}
run: |
URL="https://github.com/$REPO/releases/download/v$VERSION/Margin.Mail_${VERSION}_amd64.deb"
# From the published asset, so the hash is of the artifact users will actually fetch.
curl -fsSL --retry 3 -o package.deb "$URL"
HASH="sha256-$(openssl dgst -sha256 -binary package.deb | base64)"
jq -n --arg v "$VERSION" --arg h "$HASH" '{version: $v, hash: $h}' > nix/release.json
cat nix/release.json
- uses: cachix/install-nix-action@v31
# Building it is the check: a wrong hash, a library autoPatchelf cannot find or a broken flake
# stops here rather than on someone's machine. --impure and the variable because FSL is not a
# free licence, so nixpkgs refuses to build the package without being told.
- name: Build the package
run: NIXPKGS_ALLOW_UNFREE=1 nix build --impure .#margin-mail --print-build-logs
- name: Commit the pin
env:
VERSION: ${{ needs.prepare.outputs.version }}
run: |
git config user.name "github-actions[bot]"
git config user.email "github-actions[bot]@users.noreply.github.com"
git add nix/release.json
# A rerun after the pin already landed has nothing to commit, and the release is done.
if git diff --cached --quiet; then
echo "The flake already points at v$VERSION, nothing to push."
exit 0
fi
git commit -m "point the nix package at v$VERSION"
for attempt in 1 2 3 4 5; do
git fetch origin main
git rebase origin/main
if git push origin HEAD:main; then
break
fi
if [ "$attempt" = "5" ]; then
echo "::error::main kept advancing; could not push the nix pin after 5 attempts. The release is published; rerun this job."
exit 1
fi
echo "main advanced; rebasing and retrying ($attempt)…"
sleep 3
done