Please tag a release containing #612 (crash-protection for documentHighlight)

Hi @fwcd, thanks for cherry-picking the community-fork fix in #612 (commit `327a866d`).

The fix has been on `main` since **2025-01-18 23:22 UTC**, but no release has been tagged since — v1.3.13 was tagged **41 minutes earlier** (22:41 UTC), so every downstream packager (Mason, AUR, nix, etc.) still ships the affected version. Users hitting #599 / #600 by default through `nvim-lspconfig` + Mason therefore still see the `NoTopLevelDescriptorProvider: Should not be called` exception on every `documentHighlight` over a class/data class/enum brace.

Would it be possible to cut a v1.3.14 with just the cherry-pick? Even without a root fix in the analyzer, the crash protection alone would unblock the common default setup.

Thanks!

Review issue #612 and commit `327a866d` on `main`, then check the repository’s existing release and tag history for the procedure used after a fix lands. Done means a v1.3.14 release contains that commit so downstream packagers can consume the documentHighlight crash protection.

Written by the indexing model from the issue text.