Publish new release with updated peerDependencies (^0.22.4)

GitHub Issue Draft: tree-sitter/tree-sitter-cpp

Title: Publish new release with updated peerDependencies (^0.22.4)

The peerDependencies for tree-sitter were updated from ^0.21.1 to ^0.22.4 on master (commit 12bd6f7, Sep 2025), but v0.23.4 on npm still ships the old range.

This causes warnings for any project that depends on both tree-sitter-cpp and another tree-sitter grammar that requires tree-sitter@^0.22.x (e.g., tree-sitter-rust@0.23.3 requires ^0.22.1):

npm warn ERESOLVE overriding peer dependency
npm warn While resolving: tree-sitter-cpp@0.23.4
npm warn Found: tree-sitter@0.22.4
npm warn Could not resolve dependency:
npm warn peerOptional tree-sitter@"^0.21.1" from tree-sitter-cpp@0.23.4

Since the peer dep is marked optional and tree-sitter@0.22.4 works at runtime, there's no functional issue — just noisy install output for downstream consumers.

Could a new patch release be published to npm with the updated package.json from master?

Compare the package.json on master with the package metadata published in tree-sitter-cpp@0.23.4, focusing on the tree-sitter peerDependencies range. Confirm that the updated range is present and determine the repository's process for publishing a new npm patch release; done means the published package no longer emits the reported peer-dependency warning.