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

docs: apply auto-generated annotations to LSP configs

2026-03-13T15:39:05Z

fix(rust_analyzer): recognize std lib sources in sysroot #4338

2026-03-09T19:47:59Z

Problem: System installed sources of Rust standard library are not detected as library sources. Solution: Add sources location to paths used for library check. See also: https://rust-analyzer.github.io/book/configuration.html#cargo.sysrootSrc

fix(rust_analyzer): pass environment in rust-analyzer.runSingle #4333

2026-03-06T15:35:47Z

When rust-analyzer wants to invoke cargo (eg, when the user uses code lenses), it sends a Command to nvim. This Command contains environment info that we're currently ignoring (ie, a value of RUSTC_TOOLCHAIN). With this change, we forward the environment variables that rust-analyzer wants to set to the spawned process.

feat(rust_analyzer): enable codelens (#4210)

2025-11-22T07:18:30Z

Problem: rust_analyzer does not contain the configs for codelens by default Solution: Add codelens config

feat(rust-analyzer): out-of-the-box support for codelens #4165

2025-10-29T13:09:50Z

Codelens requires a bit of special configuration to work on rust-analyzer as described here: neovim/neovim#34353 (comment)

chore: add type annotation for configs

2025-08-19T02:39:23Z

fix(rust_analyzer): update config to 0.11+

2025-08-11T18:45:12Z

- Call request as method - Silence wrong diagnostic

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`.

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()`..

fix(rust_analyzer): scheduled vim.notify in on_exit of vim.system(#3793)

2025-04-27T10:15:32Z

Fix `E5560: nvim_echo must not be called in a fast event context`

refactor: deprecate util.validate_bufnr()

2025-04-23T13:50:22Z

ci(lint): deprecate util.path.is_descendant() on Nvim 0.11+ #3766

2025-04-23T11:48:12Z

fix: use "Lsp" prefix for config-defined commands

2025-04-21T16:47:01Z

docs: cleanup

2025-04-18T15:44:38Z

- brief should live at the top of each file - fix indentation for some docs

fix(rust_analyzer): call on_dir() when reusing client #3736

2025-04-16T17:29:55Z

fix(docs): docgen.lua reads from `lua/*.lua` #3708

2025-04-13T02:40:01Z

Problem: Since configs now live in `lsp/`, the docgen needs to be updated. Solution: Read the configs from `lsp/`. Parse the `@brief` docstring to get the docs.

feat: migrate to vim.lsp.config #3659

2025-04-12T22:15:43Z

Problem: Nvim 0.11 has vim.lsp.config, which mostly replaces the legacy nvim-lspconfig "framework". Solution: Migrate all configs to `lsp/*` variants. The old configs in `lua/lspconfig/` are "frozen". The new configs include these changes: - `commands` field became raw calls to `vim.api.nvim_buf_create_user_command` inside `on_attach`. - `root_dir` became: - `root_markers` whenever the file list was simple didn't need to mach `*` - if the logic was complicated, or needed to match something like '\*.c', it was defined as a vim.lsp.Config `root_dir` callback. - `on_config_change` became `before_init`. I don't actually know if this is the correct approach, but looking around the documentation of `nvim-lspconfig` a saw that it was defined as the function that gets called as soon as the config have `root_dir`, and so I thought `before_init` might be the closest alternative. - `docs.description` became a luadoc `@brief` docstring. - `single_file_support = false`? Co-authored-by: Aliou Diallo Co-authored-by: Justin M. Keyes