[renovate]

Why

Renovate proposes the WillBooster tree-sitter runtime 16 (@willbooster/web-tree-sitter 16.0.2 and the willbooster-tree-sitter crate 16.0.2). Runtime 16 removes the fork's query and highlighting APIs, which this grammar no longer uses, and 16.0.2 bounds the Wasm memory of ambiguous invalid input during EOF acceptance (WillBooster/tree-sitter#325).

Requirements

• required: Complete the open Renovate PRs through review and CI, investigating any failure at its root cause.
• required: A full parse of valid input yields a correct tree; invalid input yields ERROR or MISSING nodes, and parsing never crashes or hangs and takes time linear in the input size.
• required: The published Wasm grammar stays loadable by consumers on runtime 15 and 16, matching the widened @willbooster/web-tree-sitter peer range.
• chosen: Keep the Rust crate's runtime only as a dev-dependency at major 16, paired with the web runtime used in tests, because the crate itself depends only on tree-sitter-language.

Customer Summary

The npm package now declares compatibility with @willbooster/web-tree-sitter 16 as well as 15, and the installation docs name 16.0.2 as the tested runtime. Parsing behavior is unchanged.

Technical Summary

• package.json/bun.lock: the dev dependency moves to @willbooster/web-tree-sitter 16.0.2 and the peer range widens to ^15.0.0 || ^16.0.0.
• Cargo.toml/Cargo.lock: the dev-dependency willbooster-tree-sitter moves to 16 (locked at 16.0.2).
• README.md and bindings/rust/lib.rs: the tested runtime, peer range, cargo add command, and docs.rs link name 16.0.2.
• The generated parsers are unchanged; the runtime major only removed query features.

Testing

bun run verify passed locally. PR CI (test on Linux/macOS with the Wasm and native suites, test-rust, fuzz) passed on this head.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.