mirror of
https://github.com/priyanshujain/margin-calendar.git
synced 2026-10-02 19:17:04 +00:00
pj
590506eb92
Ported from margin's pipeline, with the platform list this app actually claims. Release is manual: it bumps tauri.conf.json, package.json and Cargo.toml together, tags, and then builds the tag rather than whatever main has drifted to by the time the runners pick it up. Nothing publishes until every platform lands. The last job downloads latest.json and refuses to take the release out of draft unless darwin-aarch64, darwin-x86_64 and linux-x86_64 are all present, because a half-populated manifest is worse than no release at all: the updater would offer an update to the platforms that made it and error on the ones that did not. Linux builds on Ubuntu 22.04 rather than latest. The bundle will not run on anything older than the glibc it was linked against, and 22.04 is the baseline docs/setup.md commits to. Windows is not built, matching the bundle targets and the README; adding it is a matrix entry, msi and nsis in the targets, and windows-x86_64 in the publish gate. The updater had a plugin, a capability and a menu item but no keypair and no endpoint, so releases would have produced artifacts nothing could verify. The public half is now in tauri.release.conf.json and the private half is a repository secret, alongside the Google OAuth client that build.rs embeds. Without that secret the build falls back to the example credentials and warns rather than failing, which yields an app that runs and then says Google Calendar is not set up. CI enforces the gate setup.md already names, the two test suites, and nothing more. cargo fmt --check and cargo clippy -D warnings both fail on the tree as it stands, and adopting either is a cleanup pass to decide on rather than something to bolt onto a new pipeline. justfile is the local equivalent of all this. `just install` builds for the machine it is run on and installs it, and is the same command whether or not the app is already there, so it doubles as the update. On macOS it asks a running copy to quit first, because replacing a bundle under a live process leaves it half old and half new.
71 lines
1.8 KiB
YAML
71 lines
1.8 KiB
YAML
name: CI
|
|
|
|
on:
|
|
push:
|
|
branches: [main]
|
|
pull_request:
|
|
|
|
concurrency:
|
|
group: ci-${{ github.ref }}
|
|
cancel-in-progress: true
|
|
|
|
jobs:
|
|
frontend:
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- uses: actions/checkout@v7
|
|
|
|
- uses: actions/setup-node@v6
|
|
with:
|
|
node-version: 26
|
|
|
|
- uses: pnpm/action-setup@v6
|
|
with:
|
|
version: 10
|
|
|
|
- run: pnpm install --frozen-lockfile
|
|
|
|
# `pnpm build` is tsc then vite, so this is the typecheck and the bundle in one step.
|
|
- run: pnpm build
|
|
|
|
- run: pnpm test
|
|
|
|
rust:
|
|
runs-on: ubuntu-22.04
|
|
steps:
|
|
- uses: actions/checkout@v7
|
|
|
|
- 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
|
|
|
|
- name: Install Rust
|
|
uses: dtolnay/rust-toolchain@stable
|
|
|
|
- uses: swatinem/rust-cache@v2
|
|
with:
|
|
workspaces: src-tauri -> target
|
|
|
|
# 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
|
|
run: |
|
|
mkdir -p dist && touch dist/index.html
|
|
cp google-credentials.example.json google-credentials.json
|
|
|
|
# The gate docs/setup.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: src-tauri
|
|
run: cargo test
|