Repository navigation
CICD Pipeline
What runs on a PR and how each app deploys. The workflow files in .github/workflows/ are canonical — this page is the map.
A representative set of the checks that gate a PR (see the workflows directory for the current, exact list - ~27 workflow files as of 2026-08):
| Workflow | Purpose | Gates |
|---|---|---|
CI (ci.yaml) |
The single-run pipeline (PR #1939, merged 2026-07-20): one orchestrator calling reusable stages in the same run - _core.yaml (detect affected workspaces, build shared artifacts once, lint/type-check), _test.yaml (sharded Jest suites with per-app coverage floors; includes the jest-axe a11y specs), _migration.yaml (Prisma migrations applied to a real Postgres + schema/drift validation), _sonar.yaml (scan-only SonarCloud consuming the test stage's coverage; skips Dependabot PRs), and frontend-quality.yml (bundle budgets + Lighthouse). Also runs a mobile-version preflight (scripts/mobile/version.mjs --check) and a ci-required roll-up job that aggregates every stage - published but not yet a required status check; the switchover runbook is docs/ci/required-checks-migration.md
|
all PRs, pushes to main/dev, merge queue, dispatch |
sonar-cloud-analysis |
Nightly full type-aware SonarCloud analysis (schedule + dispatch); PR/push Sonar runs as the scan-only _sonar stage inside CI — see Code Quality Gates
|
nightly cron + manual dispatch (no longer runs on PRs) |
frontend-quality |
Reusable bundle-budget + Lighthouse stage, workflow_call-only — invoked from ci.yaml, not triggered on its own |
via CI
|
frontend-e2e |
Playwright E2E | frontend-path PRs (public smoke + a11y only; the credentialed auth suite is dispatch-only behind the e2e environment after #1869) |
desktop-e2e |
Playwright-Electron E2E suite (apps/desktop/tests/e2e) |
PRs + pushes to main/dev
|
react-doctor |
React diagnostics; posts a sticky summary comment on the PR | PRs |
chromatic |
Visual regression (Storybook) | frontend changes |
codeql |
CodeQL security analysis | push (main/dev) + PRs + weekly schedule (push trigger restored by #1937) |
dependency-review |
Dependency vulnerability scan | all PRs |
secret-scan |
Gitleaks secret detection | all PRs |
pr-governance |
PR-title / conventional-commit gate | all PRs |
supply-chain |
SBOM generation (Syft, digest-pinned) + supply-chain gates - see below | PRs, merge queue, pushes to main/dev, tag pushes |
promotion-guard |
Enforces that only dev may merge into main (bot PRs auto-retargeted at dev; human override via the main-direct label) |
PRs targeting main
|
back-merge |
Opens a back-merge PR into dev on every push to main, so dev always contains main
|
pushes to main
|
Beyond the PR gates, scheduled/operational workflows include tls-expiry.yml (daily certificate-expiry check), roadmap.yml (issue-driven roadmap board sync), repo-stats.yml (nightly stats), release-notes.yml and desktop-release.yml/mobile-release.yml (see below), and deploy-api.yml (manual API deploys - see Release Process).
The former
ci-affected,frontend-a11y, anddev-docs-buildworkflows were deleted in PR #1939 — their jobs now run as stages ofci.yaml(jest-axe a11y specs run as ordinary frontend Jest specs inside the_testshards).
The PR-title gate requires a scope — a scopeless title passes local commitlint but reds the PR. See Contributing and Governance.
CI is configured to cancel in-progress runs when a branch is pushed again. A CONFLICTING/DIRTY PR silently skips pull_request-triggered Actions (only always-on scanners like GitGuardian/Aikido run) — check mergeStateStatus, merge dev, reinstall, and push before relying on CI.
Deployment is per-app and not unified — full detail in Release Process:
-
Frontend / PIMS (web): continuously deployed on every push to
main/devtouching frontend paths (cd-frontend.yaml);pims-v*tags label release points. -
Backend API: deployed via
deploy-api.yml- manualworkflow_dispatchwith adev/productionenvironment choice, concurrency-locked per host. Deploys are a decision, not a side effect of merging; deploy the API before promotingdevintomain. -
Desktop: a semver
v*tag onmain(NOTdesktop-v*- electron-updater drops non-semver tags) triggersdesktop-release.yml, which verifies the tag matchesapps/desktop/package.json(averifyjob fails the run on mismatch), then builds and signs both the macOS and Windows installers into a draft release and publishes it. -
Mobile:
mobile-v*tags triggermobile-release.yml, which builds and uploads to TestFlight and the Play internal track; promotion to the public stores stays manual. -
Release notes: auto-generated -
release-notes.ymlruns on every*-v*tag push and fills the GitHub Release body via git-cliff (cliff.toml); the process is documented in the rootRELEASING.md.
An Epic: Supply Chain Security Initiative (#1721) tracks hardening the pipeline itself:
-
SBOM generation with Syft (#1722) - delivered:
supply-chain.ymlrunsscripts/security/supply-chain.sh(Syft pinned by SHA); documented indocs/security/supply-chain.md. -
Dependabot aligned to the
devbranch (#1764) — delivered. - CI runtime reduction and de-duplication of work (#1591) — delivered by the single-run pipeline (PR #1939).
Dependabot PRs are grouped (per-ecosystem update groups in .github/dependabot.yml) and exempt from the PR-title/commitlint gate — pr-governance.yml skips dependabot[bot] (PRs #1856, #1955).
See Security for the application-security side.
Home · Architecture · ADRs · Plans · Roadmap · Contributing · Main repo · DeepWiki · Discord
Yosemite Crew is a product of DuneXploration UG (haftungsbeschränkt). This wiki mirrors the repository; where a page and the repo disagree, the repo wins. See the Wiki Style Guide.
Product & Domain
Architecture
Applications
- Backend — Overview
- Frontend / PIMS Web — Overview
- Mobile — Overview
- Desktop PIMS Shell
- Developer Portal
- SuperAdmin
Design & Accessibility
Engineering Handbook
Decisions (ADRs)
Design Docs & Plans
Meta
Canonical code & docs: main repo · Auto-generated companion: DeepWiki