releasing-an-obsidian-plugin

What problem does it solve? Releasing an Obsidian plugin involves many error-prone steps: bumping versions in manifest.json and versions.json, running full verification, tagging correctly, pushing, and confirming the GitHub Actions release actually succeeded. This Skill orchestrates that entire chain so nothing is skipped or left in a broken half-released state. ## Core Features & Use Cases - One-command release: Runs pnpm run release patch|minor|major, which chains preversion verification (format, lint, types, tests, build) with end-to-end tests against real Obsidian before anything is tagged. - Correct versioning and tagging: Bumps manifest.json, syncs versions.json, and creates a tag without a leading v so it matches what release.yml and Obsidian's community plugin process expect. - Post-push verification: Watches the e2e and release GitHub Actions workflows via the gh CLI and confirms the draft release exists with a real changelog body before declaring success. - Use Case: After merging a feature, ask the assistant to cut a minor release; it runs the release command, monitors CI across desktop and Android, and reports whether the draft GitHub release came out clean. ## Quick Start Ask the assistant to cut a new patch release of the plugin and confirm it published cleanly on GitHub.