diff --git a/docs/changes.md b/docs/changes.md index 8d6163b..32129a0 100644 --- a/docs/changes.md +++ b/docs/changes.md @@ -2,12 +2,12 @@ [中文](zh-CN/changes.md) | [English](changes.md) -What changed in each release, as a user notices it. GitHub's release pages and the pull requests linked below have the rest. The newest release is 0.2.5. When `main` is ahead of it, the changes it has are listed first, under "Unreleased", and [install-from-source.md](install-from-source.md) gets you those now. +What changed in each release, as a user notices it. GitHub's release pages and the pull requests linked below have the rest. The newest release is 0.2.6. When `main` is ahead of it, the changes it has are listed first, under "Unreleased", and [install-from-source.md](install-from-source.md) gets you those now. -## Unreleased +## 0.2.6 (2026-11-10) -- Drift detection goes through vfox's `Fingerprint` hook (needs vfox 1.1.0 or later): the plugin reports the SDK checkout's git HEAD from files only, vfox records it in the version's receipt and reports `sdk.drift` after `vfox use` and in `vfox doctor`, fixed with `vfox install --reinstall`. Linked copies from other managers (Homebrew, mise, asdf, FVM, manual installs) are covered the same way when they still carry their `.git`, as an info-level notice that vfox does not own. The plugin no longer writes `.vfox-manifest` on new vfox and no longer prints its own warning there, so the same drift is not reported twice; vfox older than 1.1.0 keeps the old warning. See [flutter-upgrade.md](flutter-upgrade.md). -- `vfox link --detect flutter` finds the Flutter SDKs that are already on the machine, from Homebrew, mise, asdf, FVM and manual installs in their usual places, and links what it finds (needs vfox 1.1.0 or later). Anything elsewhere is for `vfox link flutter@ `. +- Drift detection goes through vfox's `Fingerprint` hook ([#55](https://github.com/version-fox/vfox-flutter/pull/55)) (needs vfox 1.1.0 or later): the plugin reports the SDK checkout's git HEAD from files only, vfox records it in the version's receipt and reports `sdk.drift` after `vfox use` and in `vfox doctor`, fixed with `vfox install --reinstall`. Linked copies from other managers (Homebrew, mise, asdf, FVM, manual installs) are covered the same way when they still carry their `.git`, as an info-level notice that vfox does not own. The plugin no longer writes `.vfox-manifest` on new vfox and no longer prints its own warning there, so the same drift is not reported twice; vfox older than 1.1.0 keeps the old warning. See [flutter-upgrade.md](flutter-upgrade.md). +- `vfox link --detect flutter` finds the Flutter SDKs that are already on the machine, from Homebrew, mise, asdf, FVM and manual installs in their usual places, and links what it finds ([#55](https://github.com/version-fox/vfox-flutter/pull/55)) (needs vfox 1.1.0 or later). Anything elsewhere is for `vfox link flutter@ `. ## 0.2.5 (2026-10-21) diff --git a/docs/development.md b/docs/development.md index b16d44c..6a02705 100644 --- a/docs/development.md +++ b/docs/development.md @@ -221,7 +221,7 @@ The Linux row of the table is where the script starts to ask (storage has the SD ## Releasing -A maintainer runs **Actions → Plugin → Run workflow** on the default branch with the version, without `v`. The [README](../README.md#releasing-this-plugin) describes what the shared workflow does. Afterwards `plugins/flutter.json` in [vfox-plugins](https://github.com/version-fox/vfox-plugins) shows the version that `vfox add flutter` serves. That lags the release by hours: 1 h 22 min for 0.2.2, 4 h for 0.2.3 and 2 h 28 min for 0.2.4. Then bring the docs up to date, in both languages: move the "Unreleased" entries of [changes.md](changes.md) under the new version, dated with the day of the release, name that version as the newest one in its first paragraph, and take the "Unreleased" marks out of the other pages, see [Writing the docs](#writing-the-docs). +A maintainer runs **Actions → Plugin → Run workflow** on the default branch with the version, without `v`. The [README](../README.md#releasing-this-plugin) describes what the shared workflow does. Afterwards `plugins/flutter.json` in [vfox-plugins](https://github.com/version-fox/vfox-plugins) shows the version that `vfox add flutter` serves. That lags the release by hours: 4 h for 0.2.3, 2 h 28 min for 0.2.4 and 2 h 20 min for 0.2.5. Then bring the docs up to date, in both languages: move the "Unreleased" entries of [changes.md](changes.md) under the new version, dated with the day of the release, name that version as the newest one in its first paragraph, and take the "Unreleased" marks out of the other pages, see [Writing the docs](#writing-the-docs). ## Writing the docs diff --git a/docs/zh-CN/changes.md b/docs/zh-CN/changes.md index 9f66daa..7c1a7d9 100644 --- a/docs/zh-CN/changes.md +++ b/docs/zh-CN/changes.md @@ -2,12 +2,12 @@ [中文](changes.md) | [English](../changes.md) -每个版本改了什么,写成用户能感受到的样子。其余的细节见 GitHub 的发布页面和下面链接的 pull request。最新的发布版是 0.2.5。`main` 领先于它时,多出来的改动列在最前面的“未发布”下,想现在就用上它们,见 [install-from-source.md](install-from-source.md)。 +每个版本改了什么,写成用户能感受到的样子。其余的细节见 GitHub 的发布页面和下面链接的 pull request。最新的发布版是 0.2.6。`main` 领先于它时,多出来的改动列在最前面的“未发布”下,想现在就用上它们,见 [install-from-source.md](install-from-source.md)。 -## 未发布 +## 0.2.6 (2026-11-10) -- 漂移检查走 vfox 的 `Fingerprint` 钩子(需要 vfox 1.1.0 或更新的版本):插件只从文件读取 SDK 检出的 git HEAD 并报告,vfox 把它记在版本的收据里,`vfox use` 之后和 `vfox doctor` 里报告 `sdk.drift`,用 `vfox install --reinstall` 恢复。其他管理器(Homebrew、mise、asdf、FVM、手动安装)装出来、登记给 vfox 的 SDK,只要还带着 `.git`,同样按 info 级别的提示覆盖(vfox 不拥有它)。新版 vfox 上插件不再写 `.vfox-manifest`,也不再打印自己的警告,以免同一处漂移报两次;老于 1.1.0 的 vfox 保留旧的警告。见 [flutter-upgrade.md](flutter-upgrade.md)。 -- `vfox link --detect flutter` 会找出机器上已有的 Flutter SDK(Homebrew、mise、asdf、FVM 和手动安装在惯常位置的),找到就登记(需要 vfox 1.1.0 或更新的版本)。不在这些地方的,用 `vfox link flutter@<名字> <路径>`。 +- 漂移检查走 vfox 的 `Fingerprint` 钩子([#55](https://github.com/version-fox/vfox-flutter/pull/55))(需要 vfox 1.1.0 或更新的版本):插件只从文件读取 SDK 检出的 git HEAD 并报告,vfox 把它记在版本的收据里,`vfox use` 之后和 `vfox doctor` 里报告 `sdk.drift`,用 `vfox install --reinstall` 恢复。其他管理器(Homebrew、mise、asdf、FVM、手动安装)装出来、登记给 vfox 的 SDK,只要还带着 `.git`,同样按 info 级别的提示覆盖(vfox 不拥有它)。新版 vfox 上插件不再写 `.vfox-manifest`,也不再打印自己的警告,以免同一处漂移报两次;老于 1.1.0 的 vfox 保留旧的警告。见 [flutter-upgrade.md](flutter-upgrade.md)。 +- `vfox link --detect flutter` 会找出机器上已有的 Flutter SDK(Homebrew、mise、asdf、FVM 和手动安装在惯常位置的),找到就登记([#55](https://github.com/version-fox/vfox-flutter/pull/55))(需要 vfox 1.1.0 或更新的版本)。不在这些地方的,用 `vfox link flutter@<名字> <路径>`。 ## 0.2.5 (2026-10-21) diff --git a/docs/zh-CN/development.md b/docs/zh-CN/development.md index 0c5a55f..71e8b7d 100644 --- a/docs/zh-CN/development.md +++ b/docs/zh-CN/development.md @@ -221,7 +221,7 @@ done ## 发布 -维护者在默认分支上执行 **Actions → Plugin → Run workflow**,填入不带 `v` 的版本号。共享工作流做了什么,见 [README](../../README_CN.md#发布这个插件)。之后 [vfox-plugins](https://github.com/version-fox/vfox-plugins) 里的 `plugins/flutter.json` 会显示 `vfox add flutter` 提供的版本。这比发布晚几个小时:0.2.2 晚了 1 小时 22 分钟,0.2.3 晚了 4 小时,0.2.4 晚了 2 小时 28 分钟。然后把文档更新到位,两种语言都要:把 [changes.md](changes.md) 里“未发布”下的条目挪到新版本下面,标上发布当天的日期,在它的第一段里把新版本写成最新的发布版,并去掉其他页面里的“未发布”标记,见[编写文档](#编写文档)。 +维护者在默认分支上执行 **Actions → Plugin → Run workflow**,填入不带 `v` 的版本号。共享工作流做了什么,见 [README](../../README_CN.md#发布这个插件)。之后 [vfox-plugins](https://github.com/version-fox/vfox-plugins) 里的 `plugins/flutter.json` 会显示 `vfox add flutter` 提供的版本。这比发布晚几个小时:0.2.3 晚了 4 小时,0.2.4 晚了 2 小时 28 分钟,0.2.5 晚了 2 小时 20 分钟。然后把文档更新到位,两种语言都要:把 [changes.md](changes.md) 里“未发布”下的条目挪到新版本下面,标上发布当天的日期,在它的第一段里把新版本写成最新的发布版,并去掉其他页面里的“未发布”标记,见[编写文档](#编写文档)。 ## 编写文档