Document the release process

README.md

@@ -36,20 +36,20 @@ directory and lets you toggle which ones are tracked.
 
 ## Installation
 
-Prerequisites:
+### Python (pipx)
 
-- Python `>=3.13`
-- `uv`
-
-Setup:
+Requires Python `>=3.13`.
 
 ```bash
-uv sync --dev
+pipx install mr-manager
 ```
 
-Run:
+### From source
+
+Prerequisites: Python `>=3.13`, `uv`
 
 ```bash
+uv sync --dev
 uv run mr-manager
 ```
 
@@ -80,3 +80,4 @@ via CI.
 - [Wiki Home](https://github.com/mowi12/mr-manager/wiki)
 - [Contribution Guidelines](https://github.com/mowi12/mr-manager/wiki/Contribution-Guidelines)
 - [Troubleshooting](https://github.com/mowi12/mr-manager/wiki/Troubleshooting)
+- [Release Process](https://github.com/mowi12/mr-manager/wiki/Release-Process)

markdownlint.json

@@ -5,6 +5,7 @@
         "tables": false
     },
     "first-line-heading": false,
+    "no-duplicate-heading": false,
     "table-column-style": "aligned",
     "no-inline-html": {
         "allowed_elements": ["div", "picture", "img", "a", "h1"]

wiki/Home.md

@@ -10,6 +10,7 @@ toggle which ones should be tracked.
 
 - [Contribution Guidelines](https://github.com/mowi12/mr-manager/wiki/Contribution-Guidelines)
 - [Troubleshooting](https://github.com/mowi12/mr-manager/wiki/Troubleshooting)
+- [Release Process](https://github.com/mowi12/mr-manager/wiki/Release-Process)
 
 ## What the app does
 
@@ -25,3 +26,11 @@ toggle which ones should be tracked.
 - `k`: Move up
 - `s`: Save changes
 - `q`: Quit (with unsaved-changes confirmation when needed)
+
+## Installation
+
+| Channel       | Command                   |
+|---------------|---------------------------|
+| Python (pipx) | `pipx install mr-manager` |
+
+See the [README](https://github.com/mowi12/mr-manager#installation) for full installation instructions per channel.

wiki/Release-Process.md

@@ -0,0 +1,52 @@
+# Release Process
+
+Releases are fully automated via GitHub Actions. Pushing a version tag is the only manual step required.
+
+## Versioning
+
+This project uses [Semantic Versioning](https://semver.org/).
+Versions are derived automatically from git tags via `hatch-vcs` — there is no version field to update manually.
+
+Tag format: `vX.Y.Z` (e.g. `v1.2.0`)
+
+## Releasing a new version
+
+```bash
+git tag vX.Y.Z
+git push origin vX.Y.Z
+```
+
+That's it. The CI pipeline takes over from here.
+
+## What CI does
+
+Pushing a tag triggers the release workflow (`.github/workflows/release.yml`), which runs the following in order:
+
+`git tag` → CI Pipeline → Build Artifacts → Publish to All Channels
+
+### PyPI
+
+Builds a wheel and sdist via `uv build`, publishes via `uv publish` using OIDC trusted publishing (no token required).
+
+## Required secrets
+
+| Secret          | Used for     | Where to configure              |
+|-----------------|--------------|---------------------------------|
+| *(none — OIDC)* | PyPI publish | PyPI trusted publisher settings |
+
+## Verifying a release
+
+After the workflow completes, confirm the new version is available on each channel:
+
+### PyPI
+
+```bash
+pipx install mr-manager==X.Y.Z
+```
+
+## Troubleshooting
+
+### PyPI Publish Failed
+
+Check the Actions log for OIDC errors. Confirm the trusted publisher is configured correctly on pypi.org
+(owner, repo, workflow filename, and environment name must all match exactly).

wiki/_Sidebar.md

@@ -3,3 +3,4 @@
 - [Home](https://github.com/mowi12/mr-manager/wiki)
 - [Contribution Guidelines](https://github.com/mowi12/mr-manager/wiki/Contribution-Guidelines)
 - [Troubleshooting](https://github.com/mowi12/mr-manager/wiki/Troubleshooting)
+- [Release Process](https://github.com/mowi12/mr-manager/wiki/Release-Process)