docs: add publishing instructions for maintainers in README files

Author: CoderSerio

README.md

@@ -74,28 +74,28 @@ graph TD
 
 ## How does it works
 
-For the original Node.js, it works serially and cost lots of memory to parse os object and string into JS style: 
+For the original Node.js, it works serially and cost lots of memory to parse os object and string into JS style:
 
 ```mermaid
 graph TD
     A["JS: readdir"] -->|Call| B("Node.js C++ Binding")
     B -->|Submit Task| C{"Libuv Thread Pool"}
-    
+
     subgraph "Native Layer (Serial)"
     C -->|"Syscall: getdents"| D[OS Kernel]
     D -->|"Return File List"| C
     C -->|"Process Paths"| C
     end
-    
+
     C -->|"Results Ready"| E("V8 Main Thread")
-    
+
     subgraph "V8 Interaction (Heavy)"
     E -->|"Create JS String 1"| F[V8 Heap]
     E -->|"String 2"| F
     E -->|"String N..."| F
     F -->|"GC Pressure Rising"| F
     end
-    
+
     E -->|"Return Array"| G["JS Callback/Promise"]
 ```
 
@@ -105,25 +105,23 @@ But, it's saved with Rust now:
 graph TD
     A["JS: readdir"] -->|"N-API Call"| B("Rust Wrapper")
     B -->|"Spawn Thread/Task"| C{"Rust Thread Pool"}
-    
+
     subgraph "Rust 'Black Box'"
     C -->|"Rayon: Parallel work"| D[OS Kernel]
     D -->|"Syscall: getdents"| C
     C -->|"Store as Rust Vec<String>"| H[Rust Heap]
     H -->|"No V8 Interaction yet"| H
     end
-    
+
     C -->|"All Done"| I("Convert to JS")
-    
+
     subgraph "N-API Bridge"
     I -->|"Batch Create JS Array"| J[V8 Heap]
     end
-    
+
     J -->|Return| K["JS Result"]
 ```
 
-
-
 ## Status & Roadmap
 
 We are rewriting `fs` APIs one by one.
@@ -519,6 +517,17 @@ Optimal concurrency for `cp` is **4 threads** on Apple Silicon — beyond that,
 
 See [CONTRIBUTING.md](./CONTRIBUTING.md) for the complete development guide — from environment setup, referencing Node.js source, writing Rust implementations, to testing and benchmarking.
 
+## Publishing (Maintainers Only)
+
+`rush-fs` ships prebuilt native binaries per platform (see `optionalDependencies` in `package.json`). When cutting a release you must publish both the platform-specific packages and the main package:
+
+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`).
+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.
+
 ## License
 
 MIT

README.zh-CN.md

@@ -418,6 +418,17 @@ Rush-FS 在文件系统遍历类操作中使用多线程并行：
 
 参阅 [CONTRIBUTING.md](./CONTRIBUTING.md) — 完整的开发指南，涵盖环境搭建、参考 Node.js 源码、编写 Rust 实现、测试与性能基准。
 
+## 发布（维护者专用）
+
+`rush-fs` 会为每个平台发布一个预编译二进制（参见 `package.json` 中的 `optionalDependencies`）。要发布新版本，请依次执行：
+
+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 步可以先确认各平台包已成功发布。
+
+一旦某个平台包发布失败，修复问题后需重新执行 `pnpm prepublishOnly`，确保主包不会依赖缺失的可选依赖。
+
 ## 许可证
 
 MIT