# Release checklist (Oneirodex) > **Doc status:** Active Use before tagging a release; read the intended version from the root [`VERSION`](../../VERSION) file. ## Version bump - [ ] Root [`VERSION`](../../VERSION) matches intended semver - [ ] [`CHANGELOG.md`](../../CHANGELOG.md) has a dated section for this release - [ ] `clients/desktop/package.json`, `src-tauri/tauri.conf.json`, **`src-tauri/tauri.thin.conf.json`**, `Cargo.toml` **and `Cargo.lock`** (the lock records the crate's own version; a stale one breaks `--locked` builds); `oneirodex/__init__.py` fallback and `docs/openapi/openapi.json` - [ ] `frontend/member-app`, `frontend/admin-app`, `frontend/ops-glance`, `frontend/api-client`, `frontend/shared` package versions (npm workspaces — the single root [`package-lock.json`](../../package-lock.json) is the only lockfile; there are no per-app lockfiles to bump) - [ ] Desktop `client_version` needs no edit — it is injected from `package.json` at build time (`__APP_VERSION__`) - [ ] Release installer set is still six verified bundles (full + thin × NSIS, macOS app/DMG, DEB and AppImage); `.msi` / `.rpm` remain disabled pending native-environment verification ([desktop-code-signing.md](desktop-code-signing.md)) - [ ] `docker-compose.yml` and `docker-compose.single.yml` image tags (`APP_IMAGE`, preferred Hub `cephyrixzyth/oneirodex:X.Y.Z`; local defaults must match root `VERSION`) - [ ] Root `README.md`, `docs/README.md`, active env examples, Unraid template/library path and project release snapshot ## CI (PR gate) GitHub Actions [`.github/workflows/ci-tests.yml`](../../.github/workflows/ci-tests.yml) runs on PRs and pushes to `main` / `master` / `feature/**` (and similar). Toolchain is pinned: Python **3.12** (`.python-version`) and Node **26** (`.nvmrc`, `engines: ">=26 <27"` in every `package.json`). - **Pytest core** (Python 3.12 + Postgres service): builds the member, auth-pilot, and admin React shells, then runs `tests/ -m "not integration"` minus the named exceptions in `ci-tests.yml`, with coverage at a 65% floor and the API-envelope, print, and get-json ratchets. The gate has a 90-minute timeout; inspect the current workflow result rather than relying on historical test counts. See [`ci-gates.md`](../dev/ci-gates.md). - **Alembic (upgrade + check)** (Python 3.12 + Postgres service, independent of pytest-core): `pip install -r requirements-dev.txt`, then `python -m alembic upgrade head` and `python -m alembic check`. `check` fails hard on any diff — the baseline is kept clean by the `include_object` allow-list in `alembic/env.py` ([`alembic-baseline-notes.md`](../dev/alembic-baseline-notes.md)), so a new operation means a migration is missing. - **Lint & format** (repo root, Node 26): root `npm ci`, then `npm run lint` (ESLint flat config `eslint.config.js`) + `npm run format:check` (Prettier over `frontend/**`). - **Member-app vitest** (`frontend/member-app`): `npm test -- --run` + `npm run typecheck`. - **Admin-app vitest** (`frontend/admin-app`): `npm test -- --run` + `npm run typecheck`, plus classic theme JS harnesses and CSS token lint. - **Ops-glance vitest** (`frontend/ops-glance`): `npm test -- --run` + `npm run typecheck` **and `npm run build`** — the glance ships in the Docker image, so a broken bundle fails the gate. - **API client vitest** (`frontend/api-client`): typecheck (`npm run build`) + `npm test`. - **Shared vitest** (`frontend/shared`, `@oneirodex/ui`): `npm test` and `npm run typecheck` (`tsc --noEmit -p tsconfig.json`), including shared component, authentication-boundary and API contract checks. Both steps run in CI. - **Desktop vitest** (`clients/desktop`): six-file slice — `keychain`, `config-store`, `connection-ux`, `connect`, `launch` and `playtime-session`. The full desktop suite remains a separate local check. The repo is an npm-workspaces monorepo: the single root [`package-lock.json`](../../package-lock.json) is the only lockfile. Every JS job (`Lint & format`, the five SPA/package vitest jobs, `Desktop vitest`) caches on that root lock and installs with one repo-root `npm ci` — for the jobs that set `defaults.run.working-directory` to an app dir, that step carries an explicit `working-directory: .`. That single install reifies the whole workspace graph (every `frontend/*` app, `@oneirodex/ui`, `clients/desktop`, and the shared `typescript` / `eslint` / `prettier` toolchain); the per-job test / typecheck / build steps then run from the app dir and npm resolves up to the workspace root. Dependency bumps arrive weekly via Dependabot ([`.github/dependabot.yml`](../../.github/dependabot.yml)) for Python, the root npm workspace, Rust desktop dependencies and GitHub Actions. Python and Actions group minor, patch and major updates. npm updates are grouped by production/development dependencies for minor and patch releases; npm major updates are explicitly ignored. Rust minor/patch updates are grouped; Rust major updates remain separate for compatibility review. The CI marker set is the pull-request gate. Follow [local-postgres-pytest.md](local-postgres-pytest.md) for any additional local verification requested by the release plan. Confirm every required check is green on the exact merged commit before tagging. Before image publish: rebuild SPA `static/dist` and grep against the private banned list — [scrub-shipped-bundles.md](scrub-shipped-bundles.md) (SCRUB-7). For an unpublished container check on a disposable runner, manually dispatch **Docker publish** on the candidate branch with **preflight_only=true**. This mode builds `linux/amd64` and `linux/arm64` without a registry push, then checks fresh embedded-database startup, the served app icon and all five packaged SPA hash inventories on the native amd64 image. It uses the Docker environment template with ephemeral secrets and temporary storage; owned container removal is verified. Download `unpublished-image-preflight` for the source/version receipt. ARM64 is build-qualified by this mode; its runtime is not exercised. Normal tag publication and the final main-commit CI gates remain required. ## Verify ```bash pytest tests/test_ops_followons.py tests/test_hardlinks_ai_vr_layouts.py tests/test_q1_foundation_unit.py -q ``` - [ ] CI `ci-tests` workflow green on the release PR / commit - [ ] CI `desktop-build` green — six unsigned artifacts (full + thin × Windows / macOS / Linux); the upload fails the job if bundling produced nothing The Linux Rust job also runs the opt-in real archive disk-full check through [`test-real-game-archive-enospc.sh`](../../scripts/ci/test-real-game-archive-enospc.sh). It requires an isolated Linux GitHub runner and creates one owned 16 MiB tmpfs; it must report exactly one passing test, real kernel ENOSPC after a partial staged write, old-install preservation, retry after freeing space and `REAL_ENOSPC_CLEANUP unmounted=true removed=true`. Ordinary `cargo test` skips this fixture. Do not treat compilation, the unsupported-host refusal, or the existing simulated-full test as its positive result. This bounded native check does not qualify packaged game launches or other platforms/filesystems. - [ ] Docker build: `docker compose build` - [ ] Fresh `.env` from `.env.docker.example` starts (`SECRET_KEY` set) - [ ] Schema: `python -m alembic upgrade head` runs clean on a fresh DB and `python -m alembic check` reports no new operations (allow-list in [`docs/dev/alembic-baseline-notes.md`](../dev/alembic-baseline-notes.md)) ## Schema migrations (Alembic) Since modernization wave A3.1 ([ADR 0004](../adr/0004-adopt-alembic.md)) the schema is owned by Alembic. `oneirodex/updateschema.py` is **frozen** — new schema change means `python -m alembic revision --autogenerate -m "..."`, reviewed by hand, committed under `alembic/versions/`. Operator upgrade path is unchanged in practice: pull image → `compose up` → `init_manager` Phase 2 builds/updates the schema and, on the first boot after Alembic adoption, stamps pre-Alembic databases at the **baseline** revision (`b9ab856b09ff`, never `head`) then always runs `alembic upgrade head` so post-baseline revisions (for example scan-job schedule columns) apply without a manual operator step. Log lines: `Stamped existing schema at Alembic baseline` and `Alembic upgrade head complete`. `/awake` returns readiness after database and startup initialization checks pass. ## Publish - [ ] Commit + push release branch / PR to `main` - [ ] Git tag `vX.Y.Z` matching `VERSION` and GitHub Release notes from CHANGELOG. Pushing the tag runs six OS/flavor builds and attaches eight assets (`.exe`, `.dmg`, `.deb` and `.AppImage` for both the full and thin clients; `desktop-build.yml`, `release` job). To attach builds manually, dispatch from the default branch or the matching tag, set `release_tag` to that tag, and ensure it points to the exact build commit reachable from the default branch and an existing GitHub Release. Create the GitHub Release as soon as the tag is pushed: the `release` job confirms it exists after the builds finish and stops if it does not (create it, then re-run the failed job). The job downloads only the installer artifacts and refuses to attach anything unless it finds exactly those eight files, so diagnostics uploaded by other jobs cannot reach a release. Confirm all eight files before announcing - [ ] Push Docker image tags `:X.Y.Z` and `:latest` (when publishing images). The Docker workflow requires the version tag to match `VERSION` and its commit to be reachable from the default branch. - [ ] Unraid / docs note if env vars changed The bounded Linux/tmpfs check passed at `44da3162` in [R2058](../dev/parity-evidence/desktop-real-enospc-r2058.json), including actual partial-write ENOSPC, old-install preservation, staging cleanup, retry and fixture unmount/removal. This is not installed-app or other filesystem/platform qualification.