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: streamline release guide
tianma-if91cd734c8eba
diff --git a/docs/release.md b/docs/release.mdindex 6c5a08f2..88249d4d 100644--- a/docs/release.md+++ b/docs/release.md@@ -1,25 +1,8 @@# Release Guide-EdgeEver releases are prepared with a single local command. The command validates-the repository, creates the tracking Issue, updates versions, prepares and audits-native assets in a Draft Release, publishes the Release, and installs the final-macOS DMG matching the maintainer's Mac architecture.+## Run a Release-This process does not perform mobile store delivery. Google Play and App Store-Connect delivery is a separate, explicit operation documented in-[Mobile Store Delivery](store-delivery.md).--## Prerequisites--- Run the command on macOS from a clean `main` branch that exactly matches- `origin/main`.-- Authenticate GitHub CLI with access to `tianma-if/edgeever`.-- Commit all user-facing changes before starting the release.-- Ensure every English change bullet has a corresponding Chinese bullet.-- Decide which bilingual bullet covers every commit since the previous formal- Release. Non-user-facing commits still require an explicit exclusion reason.--## Command+Run from a clean `main` branch on macOS that matches `origin/main`:```bashbun run release -- \@@ -31,125 +14,52 @@ bun run release -- \--change-commit "abcdef1"```-Repeat `--change-en`, `--change-zh`, and `--change-commit` in matching groups-when a Release contains multiple changes. The first `--change-commit` maps to-the first English/Chinese bullet pair, the second maps to the second pair, and-so on. Use comma-separated SHAs when one bullet covers multiple commits:+Repeat `--change-en`, `--change-zh`, and `--change-commit` as matching groups.+One change may cover multiple comma-separated commits:```bash--change-commit "abcdef1,1234567"```-Every commit in the previous-formal-Release-to-`HEAD` range must be covered by-at least one bilingual bullet. Explicitly exclude a commit that has no public-user impact with a concrete reason:+Every commit since the previous formal Release must be covered. Exclude a+non-user-facing commit with a concrete reason:```bash--ignore-commit "89abcde:test-only coverage"```-The command fails before validation, Issue creation, version changes, or Draft-creation if a commit is uncovered, an exclusion has no reason, or a referenced-SHA is outside the Release range. Release version commits created by this-script are recognized automatically when resuming a Draft. The resolved mapping-and exclusion reasons are recorded in the tracking Issue for auditability, but-are not added to the public Release notes.--Repeat `--label` when the tracking Issue needs multiple labels.-Public Release notes contain only user-visible changes, their impact, and any-required upgrade or migration guidance. Type checks, build commands, signing,-notarization, and asset-audit details remain in GitHub Actions and the linked-tracking Issue instead of being repeated in the public notes.--`--bump` is required and must be selected from the user and compatibility impact-of the complete Release:--- `patch` fixes bugs or makes small security, performance, or visual improvements- without adding a new user workflow.-- `minor` adds a backward-compatible feature or a coherent group of new- capabilities.-- `major` introduces an incompatible data format, sync protocol, public API, or- deployment change. Its release notes must describe the compatibility impact- and migration path.--The command calculates the next stable version and resets lower components:-`1.6.52 + patch` becomes `1.6.53`, `+ minor` becomes `1.7.0`, and `+ major`-becomes `2.0.0`. Commit prefixes may inform the choice, but do not select it-automatically because code scope and product impact are not equivalent.--Use `--dry-run` to inspect commit coverage, the native rebuild plan, and-generated bilingual notes without changing local or GitHub state.-`--skip-install` skips the post-release DMG installation and is intended for-exceptional or non-macOS runs; normal maintainer releases should install and-launch the published application.--## Release Cadence and Platform Versions--A formal Release represents a coherent stable product batch, not an individual-commit or deployment. Related fixes should normally be grouped into one Patch-Release. A separate Patch is appropriate for urgent crashes, data-loss risks, or-security fixes. Builds between Releases use the Git commit/build label and do not-consume stable version numbers.--The root version and GitHub tag identify the overall product Release. Native-marketing versions change only when that native runtime is rebuilt. Android-`versionCode` and iOS build numbers remain independent, monotonically increasing-store build identifiers.--Stable tags and their GitHub Release titles both use `vX.Y.Z`.--When verified DMGs or an APK are reused, their original filenames and native-versions remain unchanged. Every formal Release contains separate macOS arm64-and x64 DMGs plus architecture-specific updater ZIPs. Desktop and Android update-checks derive the latest applicable version from their corresponding Release-asset instead of comparing against the overall GitHub tag. This prevents an-unchanged native client from repeatedly offering an update for a Web-only or-API-only Release.--## Automated Flow--1. Verify `main`, the working tree, GitHub authentication, the latest formal- Release, and the local/remote commit relationship.-2. Audit every commit since the latest formal Release. Require each commit to- map to a bilingual public change or an explicit non-user-facing exclusion.-3. Run Web type checking, mobile type checking, the Web production build, and- release-planning tests concurrently.-4. Calculate the explicit `patch`, `minor`, or `major` version bump, then use- `scripts/plan-native-release.mjs` to determine whether desktop and Android- assets must be rebuilt or can be reused. Only affected native versions are- updated.-5. Create a bilingual tracking Issue, commit the version changes to `main`, push,- and create a Draft Release with bilingual notes.-6. Dispatch the desktop and Android asset workflows concurrently. The desktop- workflow builds arm64 and x64 packages on matching native runners, then- combines their update metadata. Verify filenames, sizes, and checksums before- publication.-7. Publish the Release and wait only for the required desktop and Android- post-publication audits.-8. Print the Demo deployment run or workflow URL. Demo deployment continues in- the background and does not delay release completion.-9. Link and close the tracking Issue, download the final DMG matching the- maintainer Mac's architecture, verify its checksum and signature, replace- `/Applications/EdgeEver.app`, and launch it.--No Release step builds a Play AAB, starts an EAS iOS build, or uploads to a-mobile store.--The release version commit includes the standard GitHub Actions skip marker.-Draft asset workflows are dispatched explicitly, so this avoids an unnecessary-push-triggered Android build without skipping required release builds.--## Failure and Resume Behavior--- A validation or Draft asset failure leaves the Release unpublished.-- An uncovered or invalidly excluded commit stops the command before it writes- local versions or creates any GitHub Issue or Release.-- If the process stops after the version commit and Draft creation, rerun the- same command. A Draft whose version and target match the current `main` commit- is resumed instead of creating another Issue, commit, or Release.-- A failed post-publication native audit attempts to return the Release to Draft- and leaves the Issue open for correction.-- A failed application replacement restores the previous app from the macOS- Trash backup when possible.-- Demo deployment status is intentionally independent of Release completion;- use the printed Actions URL to inspect or retry it.+The coverage audit runs before any local or GitHub mutation. Its mapping is+stored in the tracking Issue, not in the public Release notes. Public notes+contain only user-visible changes, impact, and necessary migration guidance.++Use `--dry-run` to inspect commit coverage, the native rebuild plan, and notes.+Use `--skip-install` only when the published macOS application should not be+installed and launched after the Release.++## EdgeEver-Specific Behavior++- Stable tags and Release titles use `vX.Y.Z`.+- The root version identifies the product Release. Native marketing versions+ change only when that native runtime is rebuilt. Android `versionCode` and+ iOS build numbers remain independent, monotonically increasing identifiers.+- A formal Release contains macOS arm64 and x64 DMGs, architecture-specific+ updater ZIPs, and an Android arm64 APK. Unchanged native assets are reused+ with their original filenames, versions, and checksums.+- Desktop and Android update checks use the version embedded in the applicable+ Release asset rather than the overall GitHub tag. This prevents a Web-only or+ API-only Release from prompting an unnecessary native update.+- The script creates the tracking Issue and Draft Release, validates or reuses+ native assets, publishes, closes the Issue, and installs the matching DMG.+ Demo deployment continues independently after its Actions URL is printed.+- Mobile store delivery is not part of this command. See+ [Mobile Store Delivery](store-delivery.md).++## Failure and Resume++- Validation or Draft asset failures leave the Release unpublished.+- Rerunning the same command resumes a matching Draft created by an interrupted+ run instead of creating another Issue, commit, or Release.+- A failed post-publication native audit attempts to return the Release to+ Draft and leaves the Issue open.+- If application replacement fails, the script restores the previous app from+ its macOS Trash backup when possible.diff --git a/docs/release.zh-CN.md b/docs/release.zh-CN.mdindex fc3b4364..84b70eff 100644--- a/docs/release.zh-CN.md+++ b/docs/release.zh-CN.md@@ -1,22 +1,8 @@# Release 发布指南-EdgeEver 使用一条本地命令准备 Release。该命令会检查仓库、创建跟踪 Issue、-更新版本、在 Draft Release 中准备并审计原生资产、正式发布 Release,并安装与-维护者 Mac 架构匹配的最终 macOS DMG。+## 执行发布-该流程不执行移动端商店交付。Google Play 和 App Store Connect 交付是独立且-需要显式触发的操作,详见[移动端商店交付](store-delivery.zh-CN.md)。--## 前置条件--- 在 macOS 上执行,当前必须是干净的 `main` 分支,并且与 `origin/main` 完全一致。-- GitHub CLI 已完成认证,并且有权访问 `tianma-if/edgeever`。-- 开始发布前,所有面向用户的改动都已提交。-- 每条英文更新说明都必须有对应的中文说明。-- 明确上一个正式 Release 之后的每个提交由哪一组双语说明覆盖;即使提交不面向- 用户,也必须显式填写忽略原因。--## 命令+在 macOS 上从与 `origin/main` 一致且工作区干净的 `main` 分支执行:```bashbun run release -- \@@ -28,103 +14,46 @@ bun run release -- \--change-commit "abcdef1"```-如果一个 Release 包含多项改动,请按组重复传入 `--change-en`、-`--change-zh` 和 `--change-commit`。第一项 `--change-commit` 对应第一组-中英文说明,第二项对应第二组,以此类推。一条说明覆盖多个提交时,使用逗号-分隔 SHA:+多项变化需要按组重复传入 `--change-en`、`--change-zh` 和+`--change-commit`。一项变化可以关联多个以逗号分隔的提交:```bash--change-commit "abcdef1,1234567"```-从上一个正式 Release 到当前 `HEAD` 的每个提交都必须被至少一组双语说明覆盖。-没有公开用户影响的提交需要填写具体原因后显式排除:+上一个正式 Release 之后的每个提交都必须被覆盖。不面向用户的提交需要填写+具体原因后显式排除:```bash--ignore-commit "89abcde:仅增加测试覆盖"```-如果存在未覆盖提交、忽略项没有原因,或 SHA 不属于本次 Release 区间,命令会-在本地验证、创建 Issue、修改版本或创建 Draft 之前直接失败。续跑 Draft 时,-脚本生成的 Release 版本提交会被自动识别。解析后的提交映射和忽略原因会记录在-跟踪 Issue 中以便审计,但不会写入公开 Release 正文。--跟踪 Issue 需要多个 Label 时,可以重复传入 `--label`。-公开 Release 说明只包含用户可感知的变化、影响以及必要的升级或迁移提醒。-类型检查、构建命令、签名、公证和资产审计等技术细节保留在 GitHub Actions-与关联跟踪 Issue 中,不再重复写入公开说明。--`--bump` 为必填项,必须根据整个 Release 对用户和兼容性的影响选择:--- `patch`:修复问题,或进行不增加新使用流程的小幅安全、性能和视觉优化。-- `minor`:增加向后兼容的新功能,或发布一组完整的新能力。-- `major`:引入不兼容的数据格式、同步协议、公共 API 或部署变化;Release- 说明必须写明兼容性影响和迁移方式。--命令会计算下一个稳定版本并将低位归零:`1.6.52 + patch` 得到 `1.6.53`,-`+ minor` 得到 `1.7.0`,`+ major` 得到 `2.0.0`。提交前缀可以辅助判断,但-不会自动决定版本级别,因为代码改动类型不等同于产品影响。--使用 `--dry-run` 可以查看提交覆盖审计、原生端重建计划和生成的双语说明,-且不会修改本地或 GitHub 状态。`--skip-install` 会跳过发布后的 DMG 安装,-仅适用于特殊情况或非 macOS 环境;维护者正常发布时仍应安装并启动已发布的应用。--## 发布节奏与平台版本--正式 Release 代表一批完整、稳定的产品变化,而不是单个提交或单次部署。相关-修复通常应合并为一个 Patch Release;崩溃、数据丢失风险或安全问题可以紧急-单独发布。两个正式 Release 之间的构建使用 Git 提交或构建标识,不消耗稳定-版本号。--根版本和 GitHub tag 表示整体产品 Release。只有原生运行时需要重建时,才更新-对应的原生展示版本。Android `versionCode` 和 iOS Build Number 继续作为独立、-严格递增的商店构建标识。--正式 Tag 及其对应的 GitHub Release 标题均统一使用 `vX.Y.Z`。--复用已验证的 DMG 或 APK 时,保留其原始文件名和原生版本。每个正式 Release-都同时包含独立的 macOS arm64 与 x64 DMG,以及按架构区分的更新 ZIP。桌面端-和 Android 更新检查从各自在 Release 中的资产读取适用版本,而不是直接比较-整体 GitHub tag,避免原生客户端因为仅涉及 Web 或 API 的 Release 反复提示-无效更新。--## 自动化流程+覆盖审计在修改本地或 GitHub 状态之前执行。映射记录在跟踪 Issue 中,不写入+公开 Release 说明。公开说明只包含用户可感知的变化、影响和必要的迁移提醒。-1. 检查 `main`、工作区、GitHub 认证、上一个正式 Release,以及本地与远端的- 提交关系。-2. 审计上一个正式 Release 之后的全部提交,要求每个提交关联一组双语公开说明,- 或带具体原因显式标记为不面向用户。-3. 并行执行 Web 类型检查、移动端类型检查、Web 生产构建和 Release 规划测试。-4. 按显式选择的 `patch`、`minor` 或 `major` 计算版本,再使用- `scripts/plan-native-release.mjs` 判断桌面端和 Android 资产需要重建还是- 可以复用,并且只更新受影响原生端的版本。-5. 创建双语跟踪 Issue,将版本变更提交并推送到 `main`,然后创建带双语说明的- Draft Release。-6. 并行触发桌面端和 Android 资产工作流。桌面端工作流分别在匹配的原生 Runner- 上构建 arm64 与 x64 包,再合并自动更新元数据;正式发布前检查文件名、大小- 和校验和。-7. 正式发布 Release,且只等待必要的桌面端和 Android 发布后资产审计。-8. 输出 Demo 部署任务或工作流链接。Demo 在后台继续部署,不再延迟 Release- 完成。-9. 回链并关闭跟踪 Issue,下载与维护者 Mac 架构匹配的最终 DMG,验证校验和与- 签名,覆盖 `/Applications/EdgeEver.app` 并启动。+使用 `--dry-run` 查看提交覆盖、原生端重建计划和说明。仅在发布后不应安装并+启动 macOS 应用时使用 `--skip-install`。-Release 流程不会构建 Play AAB、启动 EAS iOS Build,也不会上传到移动端商店。+## EdgeEver 特有规则-版本发布提交会包含 GitHub Actions 的标准跳过标记。Draft 资产工作流由脚本-显式触发,因此可以避免一次不必要的 push 触发 Android 构建,同时不会跳过-正式发布所需的构建。+- 正式 Tag 和 Release 标题使用 `vX.Y.Z`。+- 根版本表示整体产品 Release。只有对应原生运行时重建时,才更新原生展示版本。+ Android `versionCode` 和 iOS Build Number 是相互独立且严格递增的标识。+- 每个正式 Release 包含 macOS arm64 与 x64 DMG、按架构区分的更新 ZIP,以及+ Android arm64 APK。未变化的原生资产沿用原文件名、版本和校验和。+- 桌面端和 Android 更新检查使用对应 Release 资产中记录的版本,而不是整体+ GitHub Tag,避免仅涉及 Web 或 API 的 Release 触发无效原生更新。+- 脚本负责创建跟踪 Issue 和 Draft Release、验证或复用原生资产、正式发布、+ 关闭 Issue,并安装与当前 Mac 架构匹配的 DMG。输出 Actions 链接后,Demo+ 部署会独立继续执行。+- 此命令不执行移动端商店交付,详见+ [移动端商店交付](store-delivery.zh-CN.md)。## 失败与续跑-- 本地验证或 Draft 资产失败时,Release 会保持未发布状态。-- 未覆盖的提交或格式不合法的忽略项会让命令在修改本地版本或创建任何 GitHub- Issue、Release 之前停止。-- 如果流程在版本提交和 Draft 创建后中断,重新执行同一条命令即可。脚本会识别- 版本和目标提交都与当前 `main` 匹配的 Draft,不会重复创建 Issue、提交或+- 本地验证或 Draft 资产失败时,Release 保持未发布状态。+- 中断后重新执行相同命令,会续跑匹配的 Draft,不会重复创建 Issue、提交或Release。-- 发布后的原生资产审计失败时,脚本会尝试把 Release 恢复为 Draft,并保留- Issue 供后续修复。+- 发布后的原生资产审计失败时,脚本会尝试将 Release 恢复为 Draft,并保留+ Issue。- 替换应用失败时,脚本会尽可能从 macOS 废纸篓备份恢复上一版应用。-- Demo 部署状态有意与 Release 完成状态解耦;可以通过脚本输出的 Actions 链接- 查看或重试。