docs: drop the "Unreleased" remarks after 0.5.5 (#49)

Release 0.5.5 is published, so the pages stop marking its behavior as
newer than the last release. This is the procedure of "Releasing" in
docs/development.md, in English and Chinese:

- changes.md: "Unreleased" becomes "0.5.5 (2026-11-10)", both entries
  get their pull request (#48), the sentence about the newest release
  "at the time of writing" goes, and "the new docs/managers.md"
  becomes "docs/managers.md".
- README, README_CN: the paragraph that explains "Unreleased" goes.
- managers, pnpm, troubleshooting: the "Unreleased: release 0.5.4 ..."
  remarks go. The Note row and the Warnings section now describe the
  two vfox generations without the marker.
- scenarios.md: the outputs are from "the code that became release
  0.5.5", and the shadowing bullet warns on both vfox generations
  with links to pnpm.md and managers.md, including link --detect.
- mirror.md: the User-Agent example is vfox-nodejs/0.5.5.
- source-build.md: the example URL of a released zip is 0.5.5.
- Historical "Before 0.5.4" / "Since 0.5.4" sentences stay.

Author: linghengqian

README.md

@@ -45,10 +45,6 @@ node -v
 `vfox search nodejs` lists every release, with the npm that comes with it and a
 mark on the ones of an LTS line. In an interactive terminal it lets you pick one.
 
-Behavior that only exists on `main` and not in the latest release is marked
-"Unreleased" in the pages below. [docs/changes.md](docs/changes.md) lists it, and
-[docs/source-build.md](docs/source-build.md) gets you `main`.
-
 ### Example: Ubuntu 26.04
 
 ```bash

README_CN.md

@@ -34,8 +34,6 @@ node -v
 
 `vfox search nodejs` 会列出每个版本及其自带的 npm，属于 LTS 版本线的版本带有标记。在交互式终端里可以从中选一个。
 
-只存在于 `main`、还没进入最新发布版的行为，在下面各页里标有“未发布”。[docs/zh-CN/changes.md](docs/zh-CN/changes.md) 里列出了这些行为，想直接用上 `main`，见 [docs/zh-CN/source-build.md](docs/zh-CN/source-build.md)。
-
 ### 示例：Ubuntu 26.04
 
 ```bash

docs/changes.md

@@ -4,29 +4,29 @@
 
 What changed in each release, as a user notices it. GitHub's
 [release pages](https://github.com/version-fox/vfox-nodejs/releases) list the
-pull requests. The newest release at the time of writing is 0.5.4, and `main` is
-ahead of it by everything under "Unreleased".
-[source-build.md](source-build.md) gets you those changes now.
+pull requests.
 
-## Unreleased
+## 0.5.5 (2026-11-10)
 
 - On vfox 1.1.0 and later a `node` that shadows vfox's is reported by vfox
   itself with the plugin's hint, instead of the plugin's `Note:`. Release
   0.5.4 prints `Note: <shadowing node> comes before vfox in PATH, ...` from
   `PreUse` on every vfox, so with the new vfox the same shadowing prints
   both the core warning and the plugin note. The plugin now declares
   `PLUGIN.shadowHints` for pnpm, mise, asdf, nvm, Homebrew and winget (each
-  with its handoff command and a link to `docs/pnpm.md` or the new
+  with its handoff command and a link to `docs/pnpm.md` or
   `docs/managers.md`) and keeps its own `Note:` for vfox before 1.1.0
   only, which ignores the new metadata field. See [pnpm.md](pnpm.md),
   [managers.md](managers.md) and
-  [troubleshooting.md](troubleshooting.md).
+  [troubleshooting.md](troubleshooting.md)
+  ([#48](https://github.com/version-fox/vfox-nodejs/pull/48)).
 - `vfox link --detect nodejs` links the Node.js already on the machine
   instead of downloading another copy: the nvm, mise, asdf and Homebrew
   Cellar directories with a working `node` in them, and the winget
   directory on Windows, each under the plain release number the binary
   reports. Shims, pnpm's global runtime and copies without a versioned
-  home are skipped. See [managers.md](managers.md).
+  home are skipped. See [managers.md](managers.md)
+  ([#48](https://github.com/version-fox/vfox-nodejs/pull/48)).
 
 ## 0.5.4 (2026-11-04)
 

docs/managers.md

@@ -13,9 +13,7 @@ The symptom is always the same: `vfox use nodejs@<version>` prints
 the other manager's version, because its `node` comes before vfox's in
 `PATH` (`type -a node` lists it first). On vfox 1.1.0 and later vfox
 warns itself and appends the plugin's hint for the manager it
-recognizes; on older vfox the plugin prints its own `Note:`. Unreleased:
-release 0.5.4 prints the `Note:`; on vfox 1.1.0 and later the warning
-comes from vfox itself with the plugin's hint.
+recognizes; on older vfox the plugin prints its own `Note:`.
 
 Pick at most one manager for `node` in a shell. The fastest way out is
 `vfox link --detect nodejs` (needs vfox 1.1.0 or later, which has

docs/mirror.md

@@ -95,7 +95,7 @@ with the `User-Agent` of Go's HTTP client, `Go-http-client/1.1`, and Huawei
 Cloud (HTTP 418), TUNA and BFSU (403) and USTC (204 with no content) answer that
 with an error page, or with nothing, in place of the package, which vfox saves.
 The plugin asks for `index.json` and `SHASUMS256.txt` with the `User-Agent`
-that vfox builds for it, `vfox/1.0.13 vfox-nodejs/0.5.4`, which all of them
+that vfox builds for it, `vfox/1.0.13 vfox-nodejs/0.5.5`, which all of them
 serve, and it has the download send the same one.
 
 Addresses that only redirect are not listed: on 2026-11-03

docs/pnpm.md

@@ -40,9 +40,9 @@ Observed with pnpm 12.14.0 and vfox 1.0.12 in bash on Ubuntu.
    project lookup; `node` still runs pnpm's global Node.js, not vfox's.
 
 `vfox use nodejs@<version>` warns when a `node` sits ahead of vfox
-this way, whichever tool put it there. Unreleased: release 0.5.4 prints
-the `Note:` below from the plugin; on vfox 1.1.0 and later the warning
-comes from vfox itself with the plugin's hint.
+this way, whichever tool put it there. On vfox 1.1.0 and later the warning
+comes from vfox itself with the plugin's hint; on older vfox the plugin
+prints the `Note:` below.
 
 On vfox 1.1.0 and later:
 

docs/scenarios.md

@@ -13,7 +13,7 @@ ships with Windows 10 and 11, as well as in PowerShell 7, bash, zsh and fish.
 
 Each case below says what you want, what to type and what you see. The outputs
 are from 2026-11-03 on Linux x64, with vfox 1.0.13 and the code that became
-release 0.5.4, and the home directory is shown as `/home/me`. The PowerShell
+release 0.5.5, and the home directory is shown as `/home/me`. The PowerShell
 lines were run in PowerShell 7.6.9 on Linux, except those that exist only on
 Windows: `Set-ExecutionPolicy` and the user-level
 `[Environment]::SetEnvironmentVariable`. Windows PowerShell 5.1 itself is not
@@ -129,8 +129,11 @@ What is different on Windows:
   policy of step 1, or the hook line is in the profile of the other PowerShell.
 - Only the first `node` in `PATH` runs. One from the installer of nodejs.org,
   from winget or Scoop, or from another version manager can sit in front of
-  vfox's. `vfox use` then prints a note that names it and says that it comes
-  before vfox in `PATH`, see [pnpm.md](pnpm.md). Uninstall the other one.
+  vfox's. `vfox use` then warns about it: on vfox 1.1.0 and later vfox warns
+  itself with the plugin's hint, on older vfox the plugin prints a note that
+  names it and says that it comes before vfox in `PATH`, see [pnpm.md](pnpm.md)
+  and [managers.md](managers.md). Uninstall the other one, or link it with
+  `vfox link --detect nodejs`.
 - A `.nvmrc` that Windows PowerShell 5.1 writes with `>` is UTF-16, which the
   plugin reads, see [below](#writing-the-file-from-windows-powershell-51).
 

docs/source-build.md

@@ -15,7 +15,7 @@ and `lib/` at its top level; that is the plugin package contract (see the
 [shared workflow documentation](https://github.com/version-fox/plugin-manifest-action)).
 
 A released plugin zip URL also works as `--source`, e.g.
-`vfox add --source https://github.com/version-fox/vfox-nodejs/releases/download/v0.5.4/vfox-nodejs-0.5.4.zip`.
+`vfox add --source https://github.com/version-fox/vfox-nodejs/releases/download/v0.5.5/vfox-nodejs-0.5.5.zip`.
 
 Prerequisites on all systems: [vfox](https://github.com/version-fox/vfox)
 itself plus `git`.

docs/troubleshooting.md

@@ -132,12 +132,12 @@ These are not errors.
 | `Note: Node.js versions below 16 do not support Apple Silicon (arm64), using x64 architecture with Rosetta 2` | macOS arm64 and a release before 16.0.0, see [platforms.md](platforms.md#macos) |
 | `Note: musl libc detected, installed node-v22.23.3-linux-x64-musl.tar.gz. See ...` | the plugin took the musl package, see [musl.md](musl.md) |
 | `Note: node-v18.20.8-linux-x64-musl.tar.gz is not listed in https://nodejs.org/dist/v18.20.8/, using unofficial musl build` | nodejs.org has no such musl package and the plugin takes it from unofficial-builds.nodejs.org |
-| ``Note: /home/me/.local/share/pnpm/bin/node comes before vfox in PATH, so `node` will not run nodejs@24.21.0. See ...`` | another `node` shadows vfox's on vfox before 1.1.0, see [pnpm.md](pnpm.md) for pnpm and [managers.md](managers.md) for mise, asdf, nvm, Homebrew and winget. Unreleased: release 0.5.4 prints this; on vfox 1.1.0 and later vfox warns itself (`node runs ... instead of nodejs@...`) and appends the plugin's hint |
+| ``Note: /home/me/.local/share/pnpm/bin/node comes before vfox in PATH, so `node` will not run nodejs@24.21.0. See ...`` | another `node` shadows vfox's on vfox before 1.1.0, see [pnpm.md](pnpm.md) for pnpm and [managers.md](managers.md) for mise, asdf, nvm, Homebrew and winget |
 
 ### Warnings from vfox itself
 
-Unreleased: vfox 1.1.0 and later reports a shadowing `node` with the
-plugin's hint; release 0.5.4 prints the `Note:` above from the plugin.
+On vfox 1.1.0 and later vfox reports a shadowing `node` with the
+plugin's hint; on older vfox the plugin prints the `Note:` above.
 
 | Warning | Meaning |
 | --- | --- |

docs/zh-CN/changes.md

@@ -2,12 +2,12 @@
 
 [中文](changes.md) | [English](../changes.md)
 
-按发布版本列出用户能感受到的变化。GitHub 的 [Release 页面](https://github.com/version-fox/vfox-nodejs/releases)列出了对应的 PR。写这篇文档时最新的发布版是 0.5.4，`main` 比它多出“未发布”下面的所有内容。想现在就用上这些变化，见 [source-build.md](source-build.md)。
+按发布版本列出用户能感受到的变化。GitHub 的 [Release 页面](https://github.com/version-fox/vfox-nodejs/releases)列出了对应的 PR。
 
-## 未发布
+## 0.5.5（2026-11-10）
 
-- 在 vfox 1.1.0 及以后的版本里，遮蔽 vfox 的 `node` 由 vfox 自己报告，并附带插件的提示，不再由插件打印 `Note:`。0.5.4 会在所有 vfox 上从 `PreUse` 打印 `Note: <shadowing node> comes before vfox in PATH, ...`，所以在新 vfox 上，同一个遮蔽会同时打印核心警告和插件的提示。插件现在为 pnpm、mise、asdf、nvm、Homebrew 和 winget 声明 `PLUGIN.shadowHints`（各自的交接命令，以及指向 `docs/pnpm.md` 或新建 `docs/managers.md` 的链接），只在 1.1.0 之前的 vfox 上保留自己的 `Note:`，老 vfox 会忽略这个新的元数据字段。见 [pnpm.md](pnpm.md)、[managers.md](managers.md)和 [troubleshooting.md](troubleshooting.md)。
-- `vfox link --detect nodejs` 会把本机已有的 Node.js 链进来，不用再下载一份：装着可用 `node` 的 nvm、mise、asdf 和 Homebrew Cellar 目录，Windows 上还有 winget 目录，每个都用二进制自己报出的纯版本号命名。shim、pnpm 的全局运行时和没有版本化家目录的复制会被跳过。见 [managers.md](managers.md)。
+- 在 vfox 1.1.0 及以后的版本里，遮蔽 vfox 的 `node` 由 vfox 自己报告，并附带插件的提示，不再由插件打印 `Note:`。0.5.4 会在所有 vfox 上从 `PreUse` 打印 `Note: <shadowing node> comes before vfox in PATH, ...`，所以在新 vfox 上，同一个遮蔽会同时打印核心警告和插件的提示。插件现在为 pnpm、mise、asdf、nvm、Homebrew 和 winget 声明 `PLUGIN.shadowHints`（各自的交接命令，以及指向 `docs/pnpm.md` 或 `docs/managers.md` 的链接），只在 1.1.0 之前的 vfox 上保留自己的 `Note:`，老 vfox 会忽略这个新的元数据字段。见 [pnpm.md](pnpm.md)、[managers.md](managers.md)和 [troubleshooting.md](troubleshooting.md)（[#48](https://github.com/version-fox/vfox-nodejs/pull/48)）。
+- `vfox link --detect nodejs` 会把本机已有的 Node.js 链进来，不用再下载一份：装着可用 `node` 的 nvm、mise、asdf 和 Homebrew Cellar 目录，Windows 上还有 winget 目录，每个都用二进制自己报出的纯版本号命名。shim、pnpm 的全局运行时和没有版本化家目录的复制会被跳过。见 [managers.md](managers.md)（[#48](https://github.com/version-fox/vfox-nodejs/pull/48)）。
 
 ## 0.5.4（2026-11-04）