Building new releases

[Taitava]

1. Edit CHANGELOG.md

1. Move everything that is under ## [Unreleased], under a new heading ## [version number] - release date.
2. Write - Nothing at the moment. under ## [Unreleased].
3. At the bottom of the file, add a new version comparison link line and edit the [Unreleased] line.

2. Edit README.md

• Add test results concerning the new version, under Tested platforms heading.
• If a beta test section is present, remove it, as this release will end the beta test.

3. Update version numbers in the following files

• main.ts: ShellCommandsPlugin.SettingsVersion: Only need to change if the new version changes settings structure.
• manifest.json: Field name version. (Also change minAppVersion field if needed).
• If manifest-beta.json is present, delete it, as this release will end the beta test.
• package.json: Field name version.
• versions.json: Create a new line at the top. Left side is the version of the plugin, and right side is the minimun version of Obsidian that this version supports.

4. Create a release in GitHub

1. Commit the changes made in the above sections, with a commit message being something like Release x.y.z.
2. In GitHub, go to Releases and click Draft a new release.
3. Click Choose a tag, then type the new version number to the field Find or create a new tag.
4. Enter the same version number to the Release title field.
5. To the Description field, write: See [CHANGELOG.md](https://github.com/Taitava/obsidian-shellcommands/blob/main/CHANGELOG.md).
6. Upload manifest.json, main.js and styles.css as binary attachments.
7. Click Publish release button.

5. Test upgrading

• Open a vault which has an earlier version of Shell commands installed.
• Upgrade the plugin and check that it works and has all new changes.

6. Update Distribution repository

• This is not so important, the repository is private and only used by me. It's used to keep track of changes in main.js file. In addition to this, it also holds manifest.json and styles.css files, but main.js is the most important.

7. Update stuff in GitHub

• Milestones: Close the just released milestone.

8. Update documentation

• Go through all #TODO comments in the documentation.
• Publish new pages/changes related to the released features.
• Update Roadmap.md, if any cornerstone features were released.