[sangkyoonnam]

Linked issue: #1289

Purpose of change

When tree-sitter 0.25.3 has to extract its native library, it writes it under FileChannel.lock(), and that lock throws on an already interrupted thread. TSParser's static initializer then fails and the class stays unusable in that class loader (#1289). ut-java fails this way when BashToolTest#interruptionPropagatesInsteadOfReturningToolResult is the first test to create a parser and the library has to be extracted. 0.26.6 extracts the library to a temporary file without the lock (bonede/tree-sitter-ng#133), as @wenjin272 suggested in #1289. Neither version declares dependencies, so META-INF/NOTICE only gets the new version. This supersedes the test-only warm-up in #1290.

Tests

Locally on macOS arm64:

• The interruption test run on its own, as the first parser initialization in a fresh JVM, passes on JDK 11.0.32.1, 17.0.14 and 21.0.11. With 0.25.3 the same run fails on JDK 11 and 17 with FileLockInterruptionException and ExceptionInInitializerError.
• BashToolTest (8) and BashValidatorTest (16) pass on all three JDKs with tree-sitter-bash:0.23.3.
• The full plan module on JDK 17: 649 tests, 0 failures, 3 skipped, and 8 errors, all in AgentPlanDeclareMCPServerTest (MCP initialization returns HTTP 404 locally), which fails the same way on main with 0.25.3.

API

No.

Documentation

• doc-needed
• doc-not-needed
• doc-included

Was this patch authored or co-authored using generative AI tooling?

• Yes
• No

Generated-by: Claude Code 2.1.303 (Claude Opus 5.5)

[wenjin272]

LGTM