v0.4.16

ruviz v0.4.16

Released: 2026-05-04

Highlights

• Documentation examples now match the current Rust, Python, npm, and crate APIs across the root README, package READMEs, and guides.
• scripts/check_docs.py validates Markdown links, fenced code block metadata, and explicitly checked Rust, TypeScript, and Python snippets across all tracked Markdown files.
• Root README Rust examples are now complete main.rs programs when they use ?, so copy-pasted examples compile as shown.
• Documentation validation now runs in both the pre-commit hook and the GitHub Actions docs workflow.

Version Alignment

This release keeps the published workspace packages aligned on one version:

• ruviz 0.4.16
• ruviz-web 0.4.16
• ruviz-gpui 0.4.16
• npm ruviz 0.4.16
• PyPI ruviz 0.4.16

Fixes And Maintenance

• Fixed README examples that had drifted from the current package APIs and entrypoints.
• Fixed stale optional-result examples that used ? on API calls that no longer return Result.
• Hardened Rust documentation checks so checked snippets using ? must be complete fallible main examples, and Markdown fn main() blocks cannot use ? while returning ().
• Covered all tracked Markdown files with docs validation, including crate READMEs, top-level docs, test docs, benchmark reports, Python docs, and web docs.
• Made TypeScript snippet checks independent of generated wasm bindings so docs checks can run before web artifacts are built.

Quality And Validation

This release builds on green CI for PR #72, plus targeted local checks during release prep:

• uv run python scripts/check_docs.py (147 tracked Markdown files)
• cargo test --doc
• git diff --check

References

• Changelog: CHANGELOG.md
• Previous release notes: v0.4.13
• Release workflow: .github/workflows/release.yml