Skip to content

feat!: migrate Java grammar to runtime ABI 6 - #23

Merged
exKAZUu merged 1 commit into
mainfrom
fix/runtime-abi-6
Oct 20, 2026
Merged

exKAZUu merged 1 commit into
mainfrom
fix/runtime-abi-6

Conversation

@exKAZUu

@exKAZUu exKAZUu commented Oct 20, 2026 •

Copy link
Copy Markdown
Member

Why

The published Java grammar uses ABI 1 and cannot load in the current native or Web runtime. Regenerate it with runtime 7.0.5 so Java parsing works with the shared ABI 6 runtime.

Requirements

  • required: Improve our forked tree-sitter repository and all forked grammar repositories as much as possible, ignoring backward compatibility.
  • required: Review existing issues and major upstream issues, PRs, and recent commits; check existing PRs before opening a dedicated PR from the latest main for each eligible item.
  • required: Run review-booster and complete-pr concurrently, then release and publish the changes.
  • required: Preserve correct Java parsing, incremental edits, and shipped queries in native and Web runtimes.
  • chosen: Generate and test with released runtime 7.0.5 and require its major version in the optional Web runtime peer dependency because the parser uses ABI 6.
  • chosen: Keep this PR limited to the runtime migration; existing grammar fixes already cover the upstream correctness reports reviewed in this audit.

Customer Summary

The Java grammar loads in runtime 7.0.5 in Rust, Node.js, Bun, browsers, and Cloudflare Workers. Consumers must upgrade their native or Web runtime to version 7.0.5 or a compatible later version in major version 7.

Technical Summary

Align the Rust and Web runtime dependencies and lockfiles, regenerate the compact parser tables and headers with the released 7.0.5 CLI, and update the ABI and runtime requirements in the README and Rust API documentation. Grammar rules and query definitions remain unchanged.

Testing

  • bun run build-wasm: canonical generation profile from all 151 corpus inputs and Wasm compilation passed.
  • bun run verify: passed, including type checking, linting, and code-gauge without violations.
  • bun wb test test/unit/corpus.test.ts test/unit/wasm.test.ts test/unit/runtimeVersion.test.ts test/unit/arrayTypes.test.ts test/unit/java25Declarations.test.ts test/unit/receiverParameters.test.ts test/unit/reservedKeywords.test.ts test/unit/unicodeLiterals.test.ts test/unit/performance.test.ts test/unit/incremental.test.ts: all 67 checks passed, including native/Wasm corpora, recovery scaling, and 1,000 random edit iterations per corpus case.
  • cargo test --locked: native binding and executable documentation passed.
  • bun wb test test/e2e: Chromium and both Cloudflare Worker modes passed (3 tests).
  • Loaded the generated Wasm with the Web runtime and compiled both shipped query files; highlight and class/method tag captures matched the source.
  • Full cross-platform tests and robustness checks run in PR CI.
  • Review-booster completed on the unchanged commit with no findings from three successful reviewers. Two provider routes were unavailable; full review coverage is unverified.
  • PR CI passed on the reviewed commit.

Regenerate the native and Wasm parser with runtime 7.0.5 and align the
native and Web runtime dependencies and usage instructions.

Co-authored-by: WillBooster (Codex CLI) <Codex CLI@willbooster.com>
@exKAZUu exKAZUu self-assigned this Oct 20, 2026
@exKAZUu
exKAZUu merged commit bd361a8 into main Oct 20, 2026
10 checks passed
@exKAZUu
exKAZUu deleted the fix/runtime-abi-6 branch October 20, 2026 16:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant