From 936afbfc960cd0288fe9f9678e242041c3b19e62 Mon Sep 17 00:00:00 2001 From: murashit Date: Tue, 23 Jun 2026 13:57:33 +0900 Subject: [PATCH] Clarify release version guidance --- docs/release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/release.md b/docs/release.md index b5f22722..9ba0cfd7 100644 --- a/docs/release.md +++ b/docs/release.md @@ -4,7 +4,7 @@ GitHub Releases attach only `main.js`, `manifest.json`, and `styles.css` as Obsi Release work is Jujutsu-first in a colocated Git repository; Git is still used to push the tag that triggers the GitHub Release workflow. If the checkout has not been initialized for Jujutsu yet, run `jj git init --colocate` and `jj bookmark track main --remote=origin` once. -Plugin versions use SemVer-shaped numbers for Obsidian distribution, but they are not a library API compatibility contract. Prefer patch releases for fixes, dependency updates, internal changes, and compatibility refreshes that preserve existing workflows. Prefer minor releases for user-visible capabilities, settings, workflow additions, or supported-runtime baseline changes. Reserve major releases for disruptive workflow, settings, storage, or support-policy changes. +Plugin versions use SemVer-shaped numbers for Obsidian distribution, but they are not a library API compatibility contract. Prefer patch releases for fixes, dependency updates, internal changes, and compatibility refreshes that preserve existing workflows, including routine Codex CLI app-server compatibility updates. Prefer minor releases for user-visible capabilities, settings, workflow additions, or supported-runtime baseline changes such as raising the minimum supported Obsidian app/API version. Reserve major releases for disruptive workflow, settings, storage, or support-policy changes. Create a release by preparing the next version, editing the generated release notes, committing the release changes, then running the preflight before pushing the matching tag: