Manually releasing your theme can be time-consuming and error-prone. In this guide, you'll configure your theme to use [GitHub Actions]( to automatically create a release when you create a new tag. 1. In the root directory of your theme, create a file called `release.yml` under `.github/workflows` with the following content: ```yml name: Release Obsidian theme on: push: tags: - "*" jobs: build: runs-on: ubuntu-latest steps: - uses: actions/checkout@v3 - name: Create release env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} run: | tag="${GITHUB_REF#refs/tags/}" gh release create "$tag" \ --title="$tag" \ --generate-notes \ --draft \ manifest.json theme.css ``` 2. In your terminal, commit the workflow. ```bash git add .github/workflows/release.yml git commit -m "Add release workflow" git push origin main ``` 3. Create a tag that matches the version in the `manifest.json` file. ```bash git tag -a 1.0.1 -m "1.0.1" git push origin 1.0.1 ``` - `-a` creates an [annotated tag]( - `-m` specifies the name of your release. For Obsidian plugins, this must be the same as the version. 4. Browse to your repository on GitHub and select the **Actions** tab. Your workflow might still be running, or it might have finished already. 5. When the workflow finishes, go back to the main page for your repository and select **Releases** in the sidebar on the right side. The workflow has created a draft GitHub release and uploaded the required assets as binary attachments. 6. Select **Edit** (pencil icon) on the right side of the release name. 7. Add release notes to let users know what happened in this release, and then select **Publish release**. You've successfully set up your theme to automatically create a GitHub release whenever you create a new tag. - If this is the first release for this theme, you're now ready to [[Submit your theme]]. - If this is an update to an already published theme, your users can now update to the latest version.