Release process

Purpose

High-level checklist for shipping desktop builds. Exact CI names change—verify .github/workflows or Azure pipelines in-repo.

Typical steps

1. Version bump — assembly/package version per tooling your branch uses (Git tags semver optional).
2. Build — dotnet publish for Mnemo.UI with RID matching shipping targets (e.g. win-x64).
3. Package — installer generation (Velopack appears in codebase via VelopackUpdateService; align packaging docs with the pipeline that produces artifacts).
4. Smoke test — install clean VM or disposable profile: launch, open notes path, trigger one AI path if applicable.
5. Publish artifacts — attach to GitHub Release or internal feed.
6. Communicate — changelog entries mapping user-facing docs (mnemo-docs/students/) when UX changes.

Updates channel

In-app updates depend on packaged metadata compatible with Velopack—coordinate bump metadata whenever installer layout changes.

---

Related: Setup, user-facing Installing