Releases

Current release

v0.9.1 is the current published release in the stable pre-1.0 release line. APIs, command surfaces, and storage formats may change as the product hardens, but v0.9.1 is usable for local developer workflows today.

For install instructions see Install. For the historical release notes, see GitHub Releases.

Release tag scheme

Release tags drive the GitHub release workflow. The workflow builds Linux, macOS, and Windows artifacts from a macOS runner.

See the release workflow for the full build matrix.

Post-release update checklist

After the maintainer tags a new release, the public materials must be updated in this order. This keeps site/ and the root README.md / README.zh-CN.md from drifting apart.

1. Update README.md and README.zh-CN.md: the version callout, the install section, and the Current Release Boundary block.
2. Update the version string on the home page hero and the Current release section on this page.
3. Reconcile the Roadmap: anything that landed in this release must move from Planned / Research into Shipped.
4. Run the static-validation harness (task item D8): all internal links resolve, all href targets exist, no claim contradicts README.md.
5. Open a PR titled docs(site): sync vX.Y.Z release notes referencing the iteration or release that produced the change.
6. After the PR merges, GitHub Pages publishes on its normal schedule; no separate release action is required for the site.

Public READMEs

The repository root carries the canonical user and developer READMEs that this site cross-references:

• README.md — English user and developer README.
• README.zh-CN.md — Chinese translation of the user and developer README.

If you find a contradiction between this site and the root READMEs, the root READMEs win until the discrepancy is resolved. See the delegable two-month plan for the failure-retry policy.