Release Process
Keep user-visible changes under Unreleased in the changelog during development. Then release from a clean, up-to-date master branch with one command from the repository root:
You can also request a semantic increment:
The command validates the repository and GitHub authentication, updates every workspace and release version file, regenerates derived files, runs all release checks, commits and pushes master, creates and pushes the matching annotated tag, waits for the official GitHub Actions build, and publishes the generated draft with the matching changelog notes. Workflow status and elapsed time remain visible while GitHub builds the release.
When plugin/dist is a directory symlink to a development Vault, a successful release also installs the three published assets into that linked plugin directory. It replaces only main.js, manifest.json, and styles.css; the existing data.json remains untouched.
No release PR or interactive confirmation is required. If the command is interrupted, rerun the same command: its internal recovery state safely restarts pre-commit preparation or resumes the existing commit, tag, workflow, or draft. The documentation remains current-only; the release command does not create version snapshots.