deps: bump tree-sitter from 0.26.12 to 0.26.13

AGENTS.md

@@ -728,7 +728,7 @@ half of that rationale fits it too. The exemption is about unification
 pressure and the runtime has none — the lockfile shows 25 crates
 depending on `tree-sitter-language` against one external dependent
 (`tree-sitter-perl`) for `tree-sitter` — and every manifest here already
-pins it at `=0.26.12` with the workspace resolving. Its ABI version is
+pins it at `=0.26.13` with the workspace resolving. Its ABI version is
 also what each vendored `parser.c` was generated against, so an
 accidental bump is precisely the drift the gate exists to catch.
 

CHANGELOG.md

@@ -24,6 +24,21 @@ for historical reference.
 
 ## [Unreleased]
 
+### Changed
+
+- The `tree-sitter` runtime is `=0.26.13`, up one upstream patch
+  release, pinned in lockstep across the root manifest, `enums`, the
+  five vendored `bca-tree-sitter-*` crates, and the `fuzz` lockfile.
+  `include/tree_sitter/api.h` is unchanged, so
+  `TREE_SITTER_LANGUAGE_VERSION` stays at 15 and the vendored `parser.c`
+  sources are unaffected; the Rust binding differs only by a dropped
+  `#[must_use]`, so the `Send + Sync` argument the PyO3 bindings rest on
+  is untouched. The C changes are an error-recovery fix that nests the
+  children of a re-parsed error under one `ERROR` node instead of
+  splicing them into the parent, and two query fixes (an exact-length
+  `MISSING` match and a corrected alternative-step skip) that nothing
+  here uses.
+
 ## [2.2.0] - 2026-08-29
 
 One entry below is marked **(breaking)**: the Python bindings'

Cargo.toml

@@ -56,7 +56,7 @@ authors = [
 # entries via `.workspace = true`, so any grammar bump here MUST be
 # applied to enums/Cargo.toml in lockstep (see recreate-grammars.sh).
 [workspace.dependencies]
-tree-sitter = "=0.26.12"
+tree-sitter = "=0.26.13"
 tree-sitter-bash = "=0.25.1"
 tree-sitter-c-sharp = "=0.23.5"
 tree-sitter-elixir = "=0.3.5"

big-code-analysis-py/src/node.rs

@@ -55,7 +55,7 @@
 //! the iterator's own keep-alive.
 //!
 //! `tree_sitter::Tree`, `Node`, and `TreeCursor` are `Send + Sync` under
-//! the pinned `=0.26.12`, so the pyclasses are sendable (no `unsendable`)
+//! the pinned `=0.26.13`, so the pyclasses are sendable (no `unsendable`)
 //! and compose with `ThreadPoolExecutor` fan-out like [`PyAst`] itself.
 //! That version literal is a premise, not decoration — the layouts and
 //! the `&mut self` on `Tree::edit` are what make the argument above

enums/Cargo.toml

@@ -26,7 +26,7 @@ askama = "^0.16"
 # [workspace.dependencies]. They MUST be kept in lockstep with the
 # matching block in ../Cargo.toml when grammars are bumped
 # (see recreate-grammars.sh).
-tree-sitter = "=0.26.12"
+tree-sitter = "=0.26.13"
 tree-sitter-bash = "=0.25.1"
 tree-sitter-c-sharp = "=0.23.5"
 tree-sitter-elixir = "=0.3.5"

tree-sitter-ccomment/Cargo.toml

@@ -56,4 +56,4 @@ tree-sitter-language="0.1.0"
 cc = "^1.2"
 
 [dev-dependencies]
-tree-sitter = "=0.26.12"
+tree-sitter = "=0.26.13"

tree-sitter-mozcpp/Cargo.toml

@@ -68,4 +68,4 @@ tree-sitter-cpp = "=0.23.4"
 build = ["tree-sitter-cpp"]
 
 [dev-dependencies]
-tree-sitter = "=0.26.12"
+tree-sitter = "=0.26.13"

tree-sitter-mozjs/Cargo.toml

@@ -70,4 +70,4 @@ tree-sitter-javascript = "=0.25.0"
 build = ["tree-sitter-javascript"]
 
 [dev-dependencies]
-tree-sitter = "=0.26.12"
+tree-sitter = "=0.26.13"

tree-sitter-preproc/Cargo.toml

@@ -56,4 +56,4 @@ tree-sitter-language="0.1.0"
 cc = "^1.2"
 
 [dev-dependencies]
-tree-sitter = "=0.26.12"
+tree-sitter = "=0.26.13"

tree-sitter-tcl/Cargo.toml

@@ -67,4 +67,4 @@ tree-sitter-language = "0.1.0"
 cc = "^1.2"
 
 [dev-dependencies]
-tree-sitter = "=0.26.12"
+tree-sitter = "=0.26.13"

utils/check-excluded-manifests.py

@@ -127,7 +127,7 @@
 # is about unification pressure, and the runtime has none: the lockfile
 # shows 25 crates depending on `tree-sitter-language` but only one
 # external crate (`tree-sitter-perl`) depending on `tree-sitter`, and
-# every manifest here already pins it at `=0.26.12` with the workspace
+# every manifest here already pins it at `=0.26.13` with the workspace
 # resolving. The runtime's ABI version is also what a grammar's
 # generated `parser.c` is built against, so an accidental bump is
 # exactly the drift this gate exists to catch.