AI-native knowledge base & Evernote/Obsidian alternative with instant sync & native MCP. Free on Cloudflare or self-hosted via Docker.
HTML ai-agentcloudflarecloudflare-d1cloudflare-r2cloudflare-workersdockerelectronevernoteevernote-alternativeknowledge-basemcpnote-takingobsidian-alternativeoffline-firstpersonal-knowledge-basepwaself-hostedsqlitetiptapweb-clipper
docs: clarify release version bump selection
tianma-if6066678adb94
diff --git a/AGENTS.md b/AGENTS.mdindex e216e115..9c8c0616 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -10,7 +10,7 @@## GitHub Release 约束与流程-1. **版本号与基线**:使用 `vX.Y.Z` 格式(非 Draft/Prerelease)。递增根目录 `package.json`;若含移动端修改,同步更新 `apps/mobile/app.json` 的 `expo.version` 并递增 `android.versionCode`。上一个实际 Release 为审计基线。+1. **版本号与基线**:`vX.Y.Z`(非 Draft/Prerelease)。发布须显式 `--bump patch|minor|major`(脚本不自动选级);按 SemVer 选择,**禁止因发版节奏把用户可感知的新能力或新平台压成 patch**。递增根目录 `package.json`;含移动端修改时同步 `apps/mobile/app.json` 的 `expo.version` 并递增 `android.versionCode`。上一个正式 Release 为审计基线。2. **跨平台 Release 资产**:每个正式 Release 页面必须同时包含 macOS arm64 DMG、macOS x64 DMG 和 Android arm64 APK。若本次未修改对应原生运行时代码、依赖、配置或构建工具,直接复用上一个正式 Release 中已验证的原始资产,保留原文件名与校验和,禁止仅为匹配新版本号而重命名。3. **验证命令**:必须通过 `bun run typecheck`、`bun run typecheck:mobile` 和 `bun run build:web`。4. **原生资产构建与复用**:由 `scripts/plan-native-release.mjs` 决定重建或复用;桌面资产包含 `apps/web`。修改判定规则时同步更新测试。移动端重建使用 `bun run build:android:apk:local`,签名配置保存在仓库外。diff --git a/docs/release.md b/docs/release.mdindex 88249d4d..b1e88dd8 100644--- a/docs/release.md+++ b/docs/release.md@@ -6,7 +6,7 @@ Run from a clean `main` branch on macOS that matches `origin/main`:```bashbun run release -- \- --bump minor \+ --bump patch \--issue-title "Improve the release workflow" \--label enhancement \--change-en "Run required release checks in parallel." \@@ -38,7 +38,9 @@ installed and launched after the Release.## EdgeEver-Specific Behavior-- Stable tags and Release titles use `vX.Y.Z`.+- Stable tags and Release titles use `vX.Y.Z`. Pass `--bump` explicitly and+ follow SemVer; do not compress user-visible new capabilities or new platforms+ into `patch` for release cadence (see `AGENTS.md`).- The root version identifies the product Release. Native marketing versionschange only when that native runtime is rebuilt. Android `versionCode` andiOS build numbers remain independent, monotonically increasing identifiers.diff --git a/docs/release.zh-CN.md b/docs/release.zh-CN.mdindex 84b70eff..a58e049d 100644--- a/docs/release.zh-CN.md+++ b/docs/release.zh-CN.md@@ -6,7 +6,7 @@```bashbun run release -- \- --bump minor \+ --bump patch \--issue-title "Improve the release workflow" \--label enhancement \--change-en "Run required release checks in parallel." \@@ -36,7 +36,8 @@ bun run release -- \## EdgeEver 特有规则-- 正式 Tag 和 Release 标题使用 `vX.Y.Z`。+- 正式 Tag 和 Release 标题使用 `vX.Y.Z`。`--bump` 须显式指定,按 SemVer 选择;+ 禁止因发版节奏把用户可感知的新能力或新平台压成 patch(详见 `AGENTS.md`)。- 根版本表示整体产品 Release。只有对应原生运行时重建时,才更新原生展示版本。Android `versionCode` 和 iOS Build Number 是相互独立且严格递增的标识。- 每个正式 Release 包含 macOS arm64 与 x64 DMG、按架构区分的更新 ZIP,以及diff --git a/scripts/release.mjs b/scripts/release.mjsindex 6b77ec36..a3900c4e 100644--- a/scripts/release.mjs+++ b/scripts/release.mjs@@ -49,7 +49,7 @@ export const RELEASE_VALIDATIONS = [const usage = `Usage:bun run release -- \\- --bump minor \\+ --bump patch \\--issue-title "Release issue title" \\--label bug \\--change-en "English user-facing change" \\