nvim-lspconfig/lua/lspconfig, branch dependabot/github_actions/leafo/gh-actions-lua-13

docs: update generated annotations

2026-04-23T14:31:45Z

skip-checks: true

docs: update generated annotations

2026-04-21T11:22:53Z

skip-checks: true

docs: update generated annotations

2026-04-15T04:20:54Z

skip-checks: true

docs: update generated annotations

2026-04-12T12:50:43Z

skip-checks: true

docs: update generated annotations

2026-04-10T14:26:44Z

skip-checks: true

docs: update generated annotations

2026-04-08T20:41:35Z

skip-checks: true

docs: update generated annotations

2026-04-08T15:56:09Z

skip-checks: true

docs: update generated annotations

2026-04-05T14:38:15Z

skip-checks: true

docs: update generated annotations

2026-04-03T14:56:37Z

skip-checks: true

docs: update generated annotations

2026-03-31T20:34:32Z

skip-checks: true

chore: update generated annotations

2026-03-27T10:46:03Z

skip-checks: true

chore: update generated annotations

2026-03-25T08:54:13Z

skip-checks: true

fix: prevent file leak in `root_markers_with_field()` #4355

2026-03-20T09:02:26Z

chore: update generated annotations

2026-03-19T17:05:07Z

skip-checks: true

feat(tsgo): enable inlay hints #4348

2026-03-17T01:06:49Z

chore: update generated annotations

2026-03-14T00:42:23Z

skip-checks: true

chore: update generated annotations

2026-03-13T15:38:20Z

skip-checks: true

fix: drop invalid filetypes from legacy configs #4327

2026-02-27T10:11:28Z

Problem: 78596b61 removed javascript.jsx and typescript.tsx from the lsp/ configs, but the same invalid filetypes remain in the legacy lua/lspconfig/configs/ files. These still surface in checkhealth warnings since the legacy configs get merged at runtime. Solution: remove javascript.jsx and typescript.tsx from all legacy config filetypes lists. The correct filetypes (javascriptreact, typescriptreact) are already present in each list.

fix(golangci_lint_ls): disable all output formats except JSON #4247

2026-01-27T13:25:39Z

This change set enables all possible output formats that exist for golangci-lint. This is necessary because if a user configures output formats in their `.golangci.yml` configuration (for example for CI) then this is always in addition to the ones enabled on the command line. Therefore, we manually disable all possible output formats. Currently, there doesn't exist a `golangci-lint` option to exclusively enable an output format or disable all from the config.

fix(util): root_markers_with_field should not match directories #4219

2025-11-27T17:58:49Z

docs: add deprecation notice to lua/lspconfig/configs #4189

2025-11-15T21:32:05Z

fix!: remove ocamlls #4118

2025-10-10T15:08:42Z

ocamlls was added at #76. It was because ocaml-lsp-server, which is official one, was too young. In 2025, the official one works fine. On the other hand, unofficial ocaml-language-server is not maintaned. We can no longer access its GitHub repository. Issue: #4115

fix(utils): normalize root_pattern result #4093

2025-09-23T18:56:16Z

refactor!: deprecate old framework/configs, Nvim 0.10 #4077

2025-09-18T03:30:24Z

fix(gitlab_ls): root dir ordering #4025

2025-08-22T02:14:23Z

Problem: If project had a nested child gitlab file named: .gitlab-ci.yml it would take it as root. Solution: If inside GIT repository just use git repository root as root and still keep the option for .gitlab* as fallback if there is no git repo yet.

refactor(yamlls): non-hacky way to enable formatting #4012

2025-08-19T14:43:28Z

Faking capabilities isn't necessary to enable formatting support. It's a dynamically registered capability that yamlls announces whenever yaml formatting is enabled in settings, which it isn't by default. See https://github.com/redhat-developer/yaml-language-server/blob/3821411ee8c92e5b7e5ca88f84ab443ae3b2791a/src/yamlServerInit.ts#L128 https://github.com/redhat-developer/yaml-language-server/blob/3821411ee8c92e5b7e5ca88f84ab443ae3b2791a/src/languageserver/handlers/settingsHandlers.ts#L159-L174 Fixes: 63a016437e44 ("feat(yamlls): document formatting support #4003")

fix(clangd): old config style still including proto filetype #3998

2025-08-15T00:23:14Z

Missing change from cc6b21ea16cc12df290152f02513a8bd0ed9d932.

refactor(lsp): vim.lsp.get_log_path() -> vim.lsp.log.get_filename() #3997

2025-08-14T18:31:21Z

fix(golangci_lint_ls): support v2 wrapper script #3984

2025-08-06T02:03:23Z

feat(harper): clojure filetype #3952

2025-07-17T02:06:56Z

docs: correct install command for pug lsp #3926

2025-06-24T13:47:11Z

Problem: Installing the pug lsp using the suggested method (`go get github.com/opa-oz/pug-lsp`) does not work in the latest versions of `go` and instead produces a message the "'go get' is no longer supported outside a module". Solution: Change the install command for the pug lsp to the correct command which is `go install github.com/opa-oz/pug-lsp@latest`.

fix: some `on_attach` callbacks may act on the wrong buffer #3916

2025-06-20T13:07:25Z

Problem: If a server is attached to a non-current buffer by `vim.lsp.buf_attach_client`, then the Language Server-related commands may be created in the current (wrong) buffer. Solution: Always use the `bufnr` arg provided to `on_attach`.

docs(millet): update install target to millet-ls #3903

2025-06-12T01:22:30Z

fix(helm_ls,yamlls): support custom filetype for helm-ls #3893

2025-06-08T01:20:55Z

feat(bicep): add `bicep-params` filetype #3886

2025-06-04T13:26:37Z

- Support for .bicepparam files Resolves #3885

fix(fish_lsp): various improvements #3869

2025-05-26T15:30:12Z

Apply suggestions brought up by the `fish_lsp` author: https://github.com/mason-org/mason-registry/pull/8609#issuecomment-2904347943

feat(golangci_lint_ls): add support for v1 #3865

2025-05-22T10:52:59Z

refactor: generalize insert_package_json() #3833

2025-05-10T14:42:35Z

feat(tailwindcss): add detection for Phoenix projects #3831

2025-05-10T00:44:12Z

Enhance root directory detection for the latest versions of TailwindCSS v4, which no longer require tailwind.config.* or postcss.config.*. For Phoenix projects, they are typically generated or add Tailwind installed via https://github.com/phoenixframework/tailwind which will now be detected by scanning the mix.lock file for the included package. Phoenix projects that install tailwindcss via package.json should still work.

fix(configs): eliminate some usages of root_pattern #3820

2025-05-04T21:11:18Z

Problem: `root_pattern` is not necessary for non-glob patterns. Solution: Replace non-glob cases with `vim.fs.root()`..

perf: execute sanitize_cmd only on Windows to speed up WSL #3808

2025-04-30T11:44:25Z

Co-authored-by: Justin M. Keyes

Revert "fix(configs): remove sanitize_cmd #3806

2025-04-29T21:30:38Z

This reverts commit 8bb2facd6fa664fe200d2d491f9f7734202426fd.

feat: laravel-ls #3802

2025-04-29T08:17:59Z

fix: improve typescript server path search for ts-dependent lsp #3795

2025-04-28T12:11:00Z

feat(util): support "package.json5" #3794

2025-04-27T14:13:04Z

Problem: Root detection fails when using `package.json5`. #3710 Solution: Modify `insert_package_json` to support `package.json5`.

fix(configs): remove sanitize_cmd #3778

2025-04-26T12:14:59Z

Problem: exepath is slow on WSL/Windows. Solution: Remove sanitize_cmd: absolute paths are nice, but not necessary.

refactor: deprecate util.validate_bufnr()

2025-04-23T13:50:22Z

refactor: deprecate util.path.search_ancestors()

2025-04-23T13:08:14Z

refactor: deprecate util functions

2025-04-23T12:16:00Z

docs(rpmspec): updated `cmd` and `description` #3756

2025-04-23T11:50:22Z

This change was made because the current configuration (as of today) does not actually work. This new configuration addresses that issue by updating the cmd used for executing the lsp server. As well as updating the description to instruct users on how to install `rpm-spec-language-server`.

docs(sqls): fix install instructions #3758

2025-04-22T11:42:42Z

Revert "fix(util): improve wildcard escaping" #3729

2025-04-15T14:15:25Z

This reverts commit e39da6a820d2a700904117d29f0dd476d64262cf.

fix(util): improve wildcard escaping #3690

2025-04-14T14:58:53Z

The escape_wildcards function was enhanced to handle a broader range of special characters that could cause issues when used in pattern matching. This includes additional wildcards, pattern matching characters, shell special characters, the escape character itself, and whitespace. This change provides more robust path handling throughout the codebase when dealing with file paths that contain special characters. Co-authored-by: Justin M. Keyes

feat(typos-lsp): support pyproject.toml and Cargo.toml #3707

2025-04-12T23:35:35Z

refactor: replace vim.loop with vim.uv #3703

2025-04-10T22:48:31Z

The former is deprecated in neovim 0.10. Remove the check added in 9b89ba5f158f73779cd58d0bb2783dfb40b28b0e. See: https://github.com/neovim/neovim/blob/v0.10.0/runtime/doc/deprecated.txt#L55

fix(stylelint): update root_file, filetypes #3702

2025-04-09T10:10:44Z

feat(tinymist): workspace commands #3639

2025-04-08T12:45:42Z

fix(openedge_ls): update configuration #3623

2025-04-07T09:54:07Z

* Changed Jar file name * New 'debug' attribute * Send 'init_options' object to language server

feat: bqls #3486

2025-04-06T01:44:12Z

feat: rpmspec #3568

2025-04-06T00:27:38Z

rpm-spec-language-server is the Language Server for RPM spec files https://github.com/dcermak/rpm-spec-language-server

refactor: deprecate get_active_client_by_name #3697

2025-04-06T00:17:35Z

refactor: deprecate add_hook_before/after #3695

2025-04-05T23:36:39Z

These are special-purpose functions that should never have been "public".

refactor: deprecate util.get_lsp_clients #3694

2025-04-05T23:29:56Z

refactor: deprecate util functions #3691

2025-04-05T22:49:12Z

These are only used by the old health.lua, which only exists for Nvim 0.10 back-compat.

feat: "just" lsp #3655

2025-04-05T15:59:53Z

feat(svelte): command to migrate to svelte 5 #3638

2025-04-05T15:58:47Z

Revert "fix(eslint): find closest ESLint directory to avoid version mismatch …" #3689

2025-04-05T13:14:21Z

This reverts commit 93835565a746e252b3342dbab688c22bdea81da7.

fix(eslint): find closest ESLint directory to avoid version mismatch #3686

2025-04-04T11:34:33Z

fix(tblgen): find tablegen_compile_commands.yml #3649

2025-04-02T13:42:14Z

The tblgen_lsp_server doesn't seem to load any specific compilation database server and hence we need to explicitly specify the command-line argument to pick the correct database path.

feat(ada_ls): alire.toml #3667

2025-04-02T13:39:18Z

fix(sourcekit): url & dynamic registration for `didChangeWatchedFiles` (#3681)

2025-04-02T10:05:27Z

docs: wgsl-analyzer install instructions #3670

2025-03-29T15:50:24Z

fix(postgres_lsp): re-enable single file support #3673

2025-03-29T15:18:55Z

Do not require a `postgrestools.jsonc` file in the root directory for single file support. Fixes #3672.

fix: ":checkhealth lspconfig" fails on Nvim 0.11 #3668

2025-03-27T12:56:20Z

Problem: `:checkhealth lspconfig` fails: E5009: Invalid $VIMRUNTIME: .../share/nvim/runtime Error executing lua: Vim:E21: Cannot make changes, 'modifiable' is off stack traceback: [C]: in function 'append' .../share/nvim/runtime/lua/vim/health.lua:443: in function '_check' `:checkhealth` cannot call itself recursively. And even if it did work, it would show a duplicate report since `:checkhealth vim.lsp` will also be part of the report. Solution: On Nvim 0.11, - show a deprecation message if invoked directly. - show a softer message if invoked as part of the "full report". fix #3664

fix(golangci-lint): disable stats in json output (#3665)

2025-03-27T07:47:44Z

feat: vectorcode-server (#3660)

2025-03-27T05:55:28Z

feat: alias :LspInfo to `:checkhealth vim.lsp` #3663

2025-03-26T19:13:08Z

Problem: `:checkhealth lspconfig` has no benefits vs `:checkhealth vim.lsp`. Solution: - on Nvim 0.11+, `:LspInfo` is an alias to `:checkhealth vim.lsp` instead of `:checkhealth lspconfig`. - `lua/lspconfig/health.lua` will be removed in a few months.

fix(golangci-lint): typo in command argument #3662

2025-03-26T14:38:25Z

fix: golangci-lint v2 json output #3661

2025-03-26T13:26:05Z

fix(biome): improved biomejs detection (#3650)

2025-03-25T08:45:25Z

feat: migrate postgres config to postgrestools #3657

2025-03-21T10:01:36Z

fix(ltex_plus): add latex to `enabled` settings (#3654)

2025-03-21T05:43:27Z

Problem: LSP not working with latex files. Spell checking skipped in latex files Solution: Add latex to the enabled section because even though 'tex' is the filetype the language ID is 'latex'

fix(tailwindcss): improved tailwindcss detection (#3648)

2025-03-20T11:20:36Z

Problem: The Tailwind CSS language server is enabled for any workspace containing a `.git` folder, a `node_modules` folder, or a `package.json` file, which is not ideal. Solution: Introduce a specific check for the `tailwindcss` package within `package.json` file using `insert_package_json` method from `util` (this approach is used in `eslint` config). Since the latest version of Tailwind CSS (v4) no longer requires `postcss.config.*` and `tailwind.config.*` files, these can no longer be relied upon as sole criteria for enabling Tailwind CSS LSP.

feat: add muon server for meson files(#3646)

2025-03-18T10:33:22Z

docs(qmlls): point to official sources

2025-03-16T16:20:06Z

Refers to the Qt docs for the initial link, quotes Qt's page for the description, and points to the official cgit server for the source.

chore(qml_lsp)!: remove config

2025-03-16T16:08:44Z

This project is archived. Prefer [qmlls](lua/lspconfig/configs/qmlls.lua).

fix: rename systemd-language-server to systemd_ls

2025-03-11T11:24:26Z

feat: systemd-language-server #3514

2025-03-07T12:57:13Z

docs(gleam): rewrite broken installation description (#3637)

2025-03-04T10:48:55Z

Signed-off-by: Christoph Heiss

fix(postgresql_lsp): update command to use lsp-proxy argument (#3636)

2025-03-03T09:37:28Z

Problem: The current command "postgresql_lsp" doesn't work as expected because the server requires the "lsp-proxy" argument to function properly. Solution: Update the cmd to use ("postgresql_lsp", "lsp-proxy") to correctly invoke the language server with its required arguments.

fix(bazelrc_lsp): invoke `lsp` subcommand explicitly (#3634)

2025-03-01T23:24:19Z

The bazelrc-lsp binary added other sub-commands besides the `lsp` functionality (e.g., `bazelrc-lsp format` can be used to format files from the command line). This commit updates the config such that the `bazelrc-lsp lsp` is explicitly invoked. (Currently, `bazelrc-lsp` still defaults to the `lsp` sub-command, but this default will likely be removed in a future version)

fix(bacon_ls): new configuration #3632

2025-02-28T12:22:47Z

Changed `settings` to `init_options`, as per `bacon-ls` readme.

fix(sourcekit): use textDocument/diagnostic over publishDiagnostics #3626

2025-02-26T21:45:01Z

Problem: nvim uses textDocument/publishDiagnostics over textDocument/diagnostic which results in delayed diagnostics Solution: dyanmically register textDocument/diagnostic capability

fix: fix broken rust analyzer link

2025-02-25T16:08:26Z

fix!: remove `lua` as root marker

2025-02-23T16:43:51Z

There is no good reason to have it as a root marker and it makes the configuration super convoluted. It breaks on even basic setups: opening `src/nvim/generators/hashy.lua` in the neovim repo causes `src/nvim` to be the root since there's a `lua` folder there. Instead, just make the root a flat set of markers and let users who look for a more advanced setup to adjust it in their own configurations.

feat: add air lsp (#3614)

2025-02-22T10:13:37Z

* feat: add air lsp * fix(air): use `vim.fs.root()`

feat: turbo-language-server (#3620)

2025-02-20T12:02:32Z

The language server supports writing [Turbo](https://turbo.hotwired.dev). There is a corresponding [VS Code plugin][1] with 700+ downloads. [1]: https://marketplace.visualstudio.com/items?itemName=marcoroth.turbo-lsp&ssr=false#overview

fix(lua_ls): return longest root path

2025-02-18T15:59:33Z

This commit doesn't address the case when root path == vim.env.HOME as the case lack return when it's true (#2110) Fix #3508

fix(eslint): openDoc breaks on some URLs #3615

2025-02-14T16:29:26Z

feat(r_language_server): add quarto filetype (#3617)

2025-02-14T06:18:55Z

[Quarto](https://quarto.org/) is a (more or less new) scientific and technical publishing system. There is also a [quarto filetype](https://github.com/neovim/neovim/blob/master/runtime/ftplugin/quarto.vim) which is very similar to [rmarkdown](https://rmarkdown.rstudio.com/) but has some extensions. The quarto filetype can also be used with python and julia. The r_language_server detects code chunks / blocks that use the R programming language and runs only on them.