[CoderSerio]

Problem and resulting release

The published 0.1.0 package predates the reviewed compatibility fixes on main. Prepare 0.1.1 so the native platform packages and public entry can ship those fixes together. This PR changes release metadata and documentation only; it does not publish npm packages.

• Synchronize package.json and Cargo.toml at 0.1.1 and regenerate the native loader version checks using pnpm build.
• Move the existing unreleased changes into a clearly marked 0.1.1 release-candidate section. Keep npm installation instructions pinned to the currently published 0.1.0 until publication is verified.
• Clarify selected-ref behavior for manual Release dispatch and use the fs-v release tag series in the maintainer checklist.

Compatibility and evidence

Based on main b89ddf8 (merged #33). The interleaved Node 22/24 benchmark runner and raw evidence are identical to main. No API, execution-route, dependency, or benchmark changes are introduced, so the full behavioral matrix from #33 is reused: https://github.com/vooyajs/fs/actions/runs/36996354983

Cargo.lock is intentionally ignored by this repository; the local release build regenerated its root package to 0.1.1 without adding a tracked lockfile. pnpm-lock.yaml requires no package-version-only change. The generated index.d.ts has no net change.

Validation

• Release build and TypeScript checking pass on macOS arm64, Node 22.22.0.
• Public-entry smoke passes for scan, sync/Promise line ranges preserving a leading blank line, null encoding, and structured ENOENT errors using the 0.1.1 release binding.
• Candidate documentation build passes (44 static pages); later main merge changed only benchmark evidence/SDD, not these pages.
• npm pack dry-run checks the main-package file plan; the Release workflow injects optional platform dependencies after building all four targets. This is not a registry-install test of an unpublished version.
• git diff --check passes. Existing benchmark files have zero diff from main.

Release plan and limits

After review and CI, merge this PR and explicitly select reviewed main for the manual Release workflow. Both checkout jobs use the dispatch ref. The existing NPM_TOKEN workflow publishes four native packages plus @vooya/fs, then creates fs-v0.1.1 after success. No workflow was dispatched, no secret value was read, and current token authorization has not been tested.

After successful publication, verify a clean registry install and the documented workflows, then update the release date/tag links, latest install recommendation and release/source comparison while retaining the historical 0.1.0 FAQ. No new speed claim is made.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
rush-fs-docs	Ready	Preview	Oct 2, 2026 10:45am UTC

[coderabbitai]

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 42 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: f377ff13-54dd-4e7c-a38b-172dfef609ee

📥 Commits

Reviewing files that changed from the base of the PR and between b89ddf8 and 685304b.

📒 Files selected for processing (9)

• .github/workflows/Release.yml
• CHANGELOG.md
• CONTRIBUTING.md
• Cargo.toml
• README.md
• README.zh-CN.md
• docs/content/guide/quick-start.mdx
• index.js
• package.json

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}