Link the release checklist from the changelog.

Author: nedtwigg

CHANGELOG.md

@@ -2,7 +2,11 @@
 
 All notable changes to this project will be documented in this file.
 
-The format is based on [Keep a Changelog](https://keepachangelog.com/).
+The format is based on [Keep a Changelog](https://keepachangelog.com/). Release checklist in [deploy.md](docs/specs/deploy.md).
+
+## [0.3.0] - 2026-04-10
+
+- Yet another initial release to test publishing.
 
 ## [0.2.0] - 2026-04-09
 

docs/specs/deploy.md

@@ -11,6 +11,33 @@ Every release produces three artifact groups under one version and changelog:
 | Standalone (macOS, Apple Silicon) | `.dmg` (install) + `.tar.gz` (update) | GitHub Release + Tauri updater |
 | Standalone (Linux) | AppImage + `.deb` | GitHub Release + Tauri updater |
 
+## Release checklist
+
+Human-driven steps, in order:
+
+1. **Update dependencies page** — run `node website/scripts/generate-deps.js` and review the diff in `website/src/data/dependencies.json`. Commit if changed.
+2. **Finalize changelog** — promote the `[Unreleased]` section in `CHANGELOG.md` to `[X.Y.Z]` with today's date. Write release notes covering both standalone and VSCode changes.
+3. **Bump versions** — update `version` in all three places:
+   - [standalone/src-tauri/tauri.conf.json](../../standalone/src-tauri/tauri.conf.json)
+   - [vscode-ext/package.json](../../vscode-ext/package.json)
+   - [lib/package.json](../../lib/package.json)
+4. **Commit and tag** — `git commit -m "Release vX.Y.Z"` then `git tag vX.Y.Z`.
+5. **Push** — `git push && git push origin vX.Y.Z`. This triggers CI (Stage 1).
+6. **Wait for CI** — monitor the workflow run. VSCode extension publishes automatically.
+7. **Run local signing** — `./scripts/sign-and-deploy.sh all X.Y.Z`. Plug in the PIV USB key first. The script will:
+   - Download unsigned CI artifacts
+   - Sign macOS (will prompt for `APPLE_SIGN_PASS` if not set)
+   - Sign Windows (will prompt for `EV_SIGN_PIN` if not set)
+   - Generate Tauri update manifest and copy to `website/public/standalone-latest.json`
+   - Create the GitHub Release with all signed assets
+8. **Deploy website** — commit the updated `website/public/standalone-latest.json` and deploy mouseterm.com so the updater endpoint is live.
+9. **Verify the release**
+   - Check GitHub Release assets are correct
+   - On a Mac: download the `.dmg`, open it, confirm no Gatekeeper warnings
+   - On Windows: download the `.exe` installer, confirm no SmartScreen warnings
+   - Confirm Tauri auto-updater picks up the new version (test from a previous version)
+   - Confirm VSCode extension is live on Marketplace and OpenVSX
+
 ## Versioning
 
 A single version number (`X.Y.Z`) applies to all artifacts. The version lives in three places that must stay in sync:
@@ -248,33 +275,6 @@ Generated by the local script after signing. The script copies it to `website/pu
 
 Note: the update manifest URLs include the version in the *path* (`/v0.1.0/`) but the *filenames* are stable. The manifest itself is served from `mouseterm.com/standalone-latest.json` — Cloudflare Pages analytics tracks every update check.
 
-## Release checklist
-
-Human-driven steps, in order:
-
-1. **Update dependencies page** — run `node website/scripts/generate-deps.js` and review the diff in `website/src/data/dependencies.json`. Commit if changed.
-2. **Finalize changelog** — promote the `[Unreleased]` section in `CHANGELOG.md` to `[X.Y.Z]` with today's date. Write release notes covering both standalone and VSCode changes.
-3. **Bump versions** — update `version` in all three places:
-   - [standalone/src-tauri/tauri.conf.json](../../standalone/src-tauri/tauri.conf.json)
-   - [vscode-ext/package.json](../../vscode-ext/package.json)
-   - [lib/package.json](../../lib/package.json)
-4. **Commit and tag** — `git commit -m "Release vX.Y.Z"` then `git tag vX.Y.Z`.
-5. **Push** — `git push && git push origin vX.Y.Z`. This triggers CI (Stage 1).
-6. **Wait for CI** — monitor the workflow run. VSCode extension publishes automatically.
-7. **Run local signing** — `./scripts/sign-and-deploy.sh all X.Y.Z`. Plug in the PIV USB key first. The script will:
-   - Download unsigned CI artifacts
-   - Sign macOS (will prompt for `APPLE_SIGN_PASS` if not set)
-   - Sign Windows (will prompt for `EV_SIGN_PIN` if not set)
-   - Generate Tauri update manifest and copy to `website/public/standalone-latest.json`
-   - Create the GitHub Release with all signed assets
-8. **Deploy website** — commit the updated `website/public/standalone-latest.json` and deploy mouseterm.com so the updater endpoint is live.
-9. **Verify the release**
-   - Check GitHub Release assets are correct
-   - On a Mac: download the `.dmg`, open it, confirm no Gatekeeper warnings
-   - On Windows: download the `.exe` installer, confirm no SmartScreen warnings
-   - Confirm Tauri auto-updater picks up the new version (test from a previous version)
-   - Confirm VSCode extension is live on Marketplace and OpenVSX
-
 ## Changelog
 
 A single `CHANGELOG.md` at the repo root, following [Keep a Changelog](https://keepachangelog.com/) format. The `[Unreleased]` section is promoted to `[X.Y.Z]` at release time. The release notes include both standalone and VSCode changes in one entry.