13 lines
917 B
Markdown
13 lines
917 B
Markdown
## 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>
|