add a doc for release process refresher

This commit is contained in:
2026-07-27 17:11:27 +06:00
parent ef35f26937
commit c3c1a98574
+12
View File
@@ -0,0 +1,12 @@
## Releasing new releases
- Update your `manifest.json` with your new version number, such as `1.0.1`, and the minimum Obsidian version required for your latest release.
- Update your `versions.json` file with `"new-plugin-version": "minimum-obsidian-version"` so older versions of Obsidian can download an older version of your plugin that's compatible.
- Create new GitHub release using your new version number as the "Tag version".
Use the exact version number, don't include a prefix `v`.
See here for an example: https://github.com/obsidianmd/obsidian-sample-plugin/releases
- Upload the files `manifest.json`, `main.js`, `styles.css` as binary attachments.
Note: The `manifest.json` file must be in two places, first the root path of your repository and also in the release.
- Publish the release.
From <https://github.com/obsidianmd/obsidian-sample-plugin/blob/master/README.md#releasing-new-releases>