chore(deps-dev): bump tree-sitter-language-pack from 1.17.0 to 1.20.0

[dependabot]

Bumps tree-sitter-language-pack from 1.17.0 to 1.20.0.

Release notes

Sourced from tree-sitter-language-pack's releases.

Release v1.20.0

What's Changed

• fix(intel): Swift and TypeScript declarations, configuration DataNode paths by @​robertsfeir in xberg-io/tree-sitter-language-pack#186
• feat: restore Rust extension ambiguity lookup by @​Goldziher in xberg-io/tree-sitter-language-pack#187
• chore(release): prepare 1.17.0 by @​Goldziher in xberg-io/tree-sitter-language-pack#188
• feat(intel): SQL, Justfile, Dockerfile, C, Cedar, dotenv and plist declarations by @​robertsfeir in xberg-io/tree-sitter-language-pack#190

Full Changelog: xberg-io/tree-sitter-language-pack@v1.16.0...v1.20.0

Release v1.19.1

What's Changed

• fix(intel): Swift and TypeScript declarations, configuration DataNode paths by @​robertsfeir in xberg-io/tree-sitter-language-pack#186
• feat: restore Rust extension ambiguity lookup by @​Goldziher in xberg-io/tree-sitter-language-pack#187
• chore(release): prepare 1.17.0 by @​Goldziher in xberg-io/tree-sitter-language-pack#188
• feat(intel): SQL, Justfile, Dockerfile, C, Cedar, dotenv and plist declarations by @​robertsfeir in xberg-io/tree-sitter-language-pack#190

Full Changelog: xberg-io/tree-sitter-language-pack@v1.16.0...v1.19.1

Release v1.19.0

Changed

• Upgraded the tree-sitter runtime to 0.27, moving tree-sitter-language to 0.1.8 in the same step. The two pins are not independent: 0.27 requires tree-sitter-language ^0.1.8, and 0.1.8 relocates the 0.26 WASM shims under wasm/unsupported/ so they no longer compile against the older runtime. The grammar ABI is unchanged -- both 0.26 and 0.27 are TREE_SITTER_LANGUAGE_VERSION 15 with a minimum compatible version of 13 -- so every bundled grammar loads exactly as before and no regeneration is implied.
• Consumers that also depend on tree-sitter directly must move to 0.27 in the same step. The tree-sitter crate declares links = "tree-sitter", and Cargo permits only one package per links value in a dependency graph, so pairing this release with a 0.26 pin fails to resolve rather than failing to compile. Nothing this crate exports changed: the requirement is a dependency floor, not a break in its own API.
• Grammar scanners now compile with NDEBUG on wasm32. 0.27's WASM libc is a documented subset that excludes assert, so a scanner keeping its assertions emitted an unresolved __assert_fail. That became an env module import rather than a link error, and the package then failed to load at runtime with Cannot find module 'env'. Native builds keep their assertions.
• Dropped this crate's own WASM libc shims (memchr, strcmp, iswalnum and friends) now that 0.27 defines them. Keeping both made the two definitions collide at link time, which broke the WASM package under the split-codegen-unit settings the release build uses.
• Replaced the 0.26 WASM integration, which used a separate non-thread-safe allocator and an incomplete libc. 0.27 supplies its own WASM libc and forwards C allocation to the Rust application's global allocator.

Fixed

• Swift binaries again link a single tree-sitter C runtime. SwiftPM builds tree-sitter 0.25.10 for SwiftTreeSitter as loose object files, while this package's Rust staticlib carries the 0.27 runtime in one archive member. Archive members load only to resolve an undefined symbol, and

... (truncated)

Changelog

Sourced from tree-sitter-language-pack's changelog.

[1.20.0] - 2026-09-14

Changed

• BREAKING (Java): enum constants are now UPPER_SNAKE_CASE. StructureKind.Function becomes StructureKind.FUNCTION, and likewise across CommentKind, DataNodeKind, DiagnosticSeverity, DocstringFormat, ExportKind and SymbolKind. The serialized wire values are unchanged, so no data migration is needed and persisted JSON stays readable; only Java source naming the old identifiers has to be updated.
• BREAKING (Swift): process() returns typed value types instead of opaque Rust handles. ProcessResult, StructureItem, DataNode and fifteen other types are now Codable structs with stored properties rather than typealiases to swift-bridge handles. Field access moves from method to property syntax (result.structure, not result.structure()), collections are real Swift arrays, and StructureKind / SymbolKind / DocstringFormat are Swift enums with associated values rather than strings. Values now cross the bridge as JSON and are decoded in Swift, so process() is throws on malformed input rather than returning a handle that fails on first access.
• Regenerate all bindings, fixtures, documentation and release workflows with Alef 0.87.1 (was 0.85.15), lifting the hold recorded in 1.19.1. 0.86.1 promoted the Swift binding to value types but left the Swift e2e suite it generates calling the old method syntax; 0.87.0 fixed that but emitted enums whose Codable conformance could not read serde's wire format. Both are resolved in 0.87.1.

Added

• Swift structure-extraction test coverage. Every test in the Swift package suite previously read only scalar fields off process(), leaving the structure path unexercised — all seventeen passed against an Alef 0.87.0 build whose process() threw on any source containing structure. The new test asserts the decoded StructureKind cases and item names, which is what exercises the element decoder; nim cannot cover this (its grammar uses none of the node kind names structure_kind_at() matches) so it goes through mojo, already in the package's statically compiled language set.

Fixed

• Swift enums with associated values decode serde's externally tagged wire format. Unit variants serialize as a bare string ("Function") and payload variants as a single-keyed object ({"Other": "macro"}); the generated conformance previously fell through to Swift's synthesized Codable, which expects {"function": {}} and matched neither form. (Alef 0.87.1)
• Node and WebAssembly e2e suites read internally tagged FormatMetadata as the flattened shape serde actually emits, with the sibling-field form asserted directly so a regression to the nested form fails loudly instead of silently degrading to the variant name. (Alef 0.87.1)
• The Go binding pairs native error messages with their sentinels, so callers can match with errors.Is while still reading the detail the native layer produced. (Alef 0.87.1)

[1.19.1] - 2026-09-13

Changed

• Alef stays pinned at 0.85.15. 0.86.1 rewrites the Swift binding to real value types -- DataNode, ProcessResult and StructureItem become Codable structs with typed properties instead of typealiases to opaque Rust handles -- but does not update the Swift e2e suite it generates alongside them, which still calls result.language() and result.structure() on

... (truncated)

Commits

• f4b24ec chore(swift): update Package.swift with checksum for v1.20.0
• 5472338 chore(release): prepare 1.20.0 with alef 0.87.1
• 3b85261 test(swift): cover structure extraction via mojo
• 312106b fix(release): stage alef.toml in the zig hash refresh
• e12c872 chore(zig): refresh test_apps package hashes for v1.19.1
• 481753f fix(swift): include stddef.h for NULL in the RustBridgeC shim
• f5f9f78 fix(swift): re-stamp the RustBridge files alef owns
• e57a51f fix(swift): restore the alef stamps the swift-bridge build strips
• 1605195 fix(alef): hold the generator at 0.85.15 for 1.19.1
• f070230 chore(release): 1.19.1
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)