chore: bump version to 0.0.3 and update publishing instructions in README files

Author: CoderSerio

.github/workflows/CI.yml

@@ -264,19 +264,21 @@ jobs:
       - name: List packages
         run: ls -R ./npm
         shell: bash
-      - name: Publish
+      - name: Publish platform packages and main package
         run: |
-          npm config set provenance true
-          if git log -1 --pretty=%B | grep "^[0-9]\+\.[0-9]\+\.[0-9]\+$";
-          then
+          COMMIT_MSG=$(git log -1 --pretty=%B)
+          if echo "$COMMIT_MSG" | grep -qE "^[0-9]+\.[0-9]+\.[0-9]+$"; then
+            npm config set provenance true
             echo "//registry.npmjs.org/:_authToken=$NPM_TOKEN" >> ~/.npmrc
+            pnpm prepublishOnly
             npm publish --access public
-          elif git log -1 --pretty=%B | grep "^[0-9]\+\.[0-9]\+\.[0-9]\+";
-          then
+          elif echo "$COMMIT_MSG" | grep -qE "[0-9]+\.[0-9]+\.[0-9]+"; then
+            npm config set provenance true
             echo "//registry.npmjs.org/:_authToken=$NPM_TOKEN" >> ~/.npmrc
+            pnpm prepublishOnly
             npm publish --tag next --access public
           else
-            echo "Not a release, skipping publish"
+            echo "Not a release (commit message is not a version), skipping publish"
           fi
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

Cargo.toml

@@ -3,7 +3,7 @@
 authors = []
 edition = "2021"
 name    = "rush_fs"
-version = "0.0.2"
+version = "0.0.3"
 
 [lib]
 crate-type = ["cdylib"]

README.md

@@ -530,11 +530,11 @@ See [CONTRIBUTING.md](./CONTRIBUTING.md) for the complete development guide —
 }
 ```
 
-Then publish both the platform-specific packages and the main package:
+Then publish both the platform-specific packages and the main package **in order**:
 
 1. Ensure you are logged in to npm (`npm login`).
-2. Bump the version via `pnpm version <patch|minor|major>` (this runs `pnpm preversion` to build the release binaries).
-3. Publish every optional dependency in `package.json` by running `pnpm prepublishOnly` (which executes `napi prepublish -t npm` and pushes `rush-fs-<platform>` packages such as `rush-fs-darwin-arm64`).
+2. Bump the version via `pnpm version <patch|minor|major>`. This runs `pnpm preversion`, which builds the `.node` artifacts under `npm/` for each platform. **These files must exist before the next step can publish them.**
+3. Run `pnpm prepublishOnly` (which runs `napi prepublish -t npm`) to publish each built package from `npm/` (e.g. `rush-fs-darwin-arm64`, `rush-fs-win32-x64-msvc`). **If you see "doesn't exist" here, you skipped the build—run `pnpm build` or complete step 2 first.**
 4. Publish the main package with `pnpm publish --access public`. The `prepublishOnly` hook runs automatically, but running step 3 manually lets you verify each platform succeeded before tagging the main release.
 
 If any platform publish fails, fix it and re-run `pnpm prepublishOnly` before retrying `pnpm publish` so consumers never receive a release referring to missing optional dependencies.

README.zh-CN.md

@@ -420,14 +420,34 @@ Rush-FS 在文件系统遍历类操作中使用多线程并行：
 
 ## 发布（维护者专用）
 
-`rush-fs` 会为每个平台发布一个预编译二进制（参见 `package.json` 中的 `optionalDependencies`）。要发布新版本，请依次执行：
+`rush-fs` 会为每个平台发布一个预编译二进制（参见 `package.json` 中的 `optionalDependencies`）。**若只有 Mac，无法本地构建 Windows/Linux 的 .node，请用下面的「通过 CI 发布」。**
 
-1. 确保已执行 `npm login`。
-2. 使用 `pnpm version <patch|minor|major>` 提升版本号（内部会运行 `pnpm preversion`，构建 release 产物）。
-3. 运行 `pnpm prepublishOnly`（即 `napi prepublish -t npm`）逐个发布 `rush-fs-<platform>` 可选依赖，例如 `rush-fs-darwin-arm64`、`rush-fs-win32-x64-msvc` 等。
-4. 最后执行 `pnpm publish --access public` 发布主包。`prepublishOnly` 会自动触发，但提前单独跑第 3 步可以先确认各平台包已成功发布。
+### 通过 GitHub Actions 发布（推荐）
+
+CI 已在多平台（macOS x64/arm64、Windows、Linux）构建并测试，通过后可由同一 workflow 发布到 npm。
+
+1. 在仓库 **Settings → Secrets and variables → Actions** 里添加 **NPM_TOKEN**（npm 账号生成的 Classic Token，需允许发布）。
+2. 确保 `package.json` 和 `Cargo.toml` 中版本号一致（如 `0.0.3`），且 `package.json` 里已包含四个 `optionalDependencies`（版本与主包一致）。
+3. 提交并推送到 `main`，**且该次提交的 commit message 仅为版本号**（如 `0.0.3`）。CI 跑通后会自动：先发布四个平台包，再发布主包 `rush-fs`。
 
-一旦某个平台包发布失败，修复问题后需重新执行 `pnpm prepublishOnly`，确保主包不会依赖缺失的可选依赖。
+示例：
+
+```bash
+# 版本和 optionalDependencies 已改好后
+git add package.json Cargo.toml
+git commit -m "0.0.3"
+git push origin main
+```
+
+4. 发版完成后，若希望 CI 继续用 `pnpm install --frozen-lockfile`，可在仓库里删掉 `optionalDependencies` 再提交，下次发版前再加回。
+
+### 本地发布（需能构建各平台）
+
+若本机可构建所有平台（或只发当前平台），可按顺序执行：
+
+1. 确保已执行 `npm login`。
+2. 使用 `pnpm version <patch|minor|major>` 提升版本号（会执行 `pnpm preversion` 在 `npm/` 下构建）。
+3. 运行 `pnpm prepublishOnly` 发布各平台包，再执行 `pnpm publish --access public` 发布主包。
 
 ## 许可证
 

package.json

@@ -1,6 +1,6 @@
 {
   "name": "rush-fs",
-  "version": "0.0.2",
+  "version": "0.0.3",
   "description": "High-performance drop-in replacement for Node.js fs module, powered by Rust",
   "main": "index.js",
   "repository": {
@@ -113,5 +113,11 @@
     "singleQuote": true,
     "arrowParens": "always"
   },
-  "packageManager": "pnpm@9.15.4"
+  "packageManager": "pnpm@9.15.4",
+  "optionalDependencies": {
+    "rush-fs-win32-x64-msvc": "0.0.3",
+    "rush-fs-darwin-x64": "0.0.3",
+    "rush-fs-linux-x64-gnu": "0.0.3",
+    "rush-fs-darwin-arm64": "0.0.3"
+  }
 }