Tya v0.53 Release Notes

Status: shipped. tya version reports 0.53.0 and ROADMAP.md carries the matching Released entry.

TL;DR

v0.53 promotes tya lsp from MVP to a full IDE-grade server: cross-file definition, references, rename, range formatting, code actions, semantic tokens, document and workspace symbols, plus incremental document sync. Setup recipes ship for Neovim, Zed, and Emacs. The language surface is unchanged from v0.52.

What’s new

LSP feature additions

New editor recipes

Editor Path
Neovim (nvim-lspconfig) editors/neovim/
Zed editors/zed/
Emacs (eglot / lsp-mode) editors/emacs/

Each recipe is a short README plus a single drop-in config file that points the editor at the system tya binary as the LSP server.

VS Code extension

editors/vscode/package.json is bumped to 0.53.0. The README and manifest already pick up every new feature via vscode-languageclient because all changes are server-side. Manual install instructions remain identical:

cd editors/vscode
npm install
npm run compile
npx vsce package
code --install-extension tya-0.53.0.vsix

Marketplace publication (publisher registration, signed VSIX, icon, GH Actions release pipeline) is queued for v0.54+.

Compatibility

Migration

Nothing required. Optional:

  1. Upgrade to v0.53 (brew install komagata/tap/tya or build from source).
  2. Re-build the VS Code extension once with npm run compile && npx vsce package and install the new VSIX. (No package.json changes mean an old VSIX still works against the new server.)
  3. New editor recipes:
    • Neovim: copy editors/neovim/init.lua.example into your config.
    • Zed: merge editors/zed/extension.json.example into ~/.config/zed/settings.json.
    • Emacs: copy editors/emacs/setup.el.example.

Implementation notes

Tests

tests/lsp_v2_test.go adds 11 subprocess scenarios that share the tests/lsp_helper.go harness from v0.52. The 7 original v0.52 cases continue to pass.

Looking ahead (v0.54+ candidates)

From ROADMAP.md § Future Work § Toolchain:

Self-host work (ROADMAP.md § Scheduled M8 / M9 / M10) remains deferred until the v1.0.0 prep window.