Deprecated `supports_method` and `jump_to_location`

[onosendi]

Description

• WARNING client.supports_method is deprecated. Feature will be removed in Nvim 0.13
  • ADVICE:
    • use client:supports_method instead.
    • stack traceback: /Users/work/.local/share/nvim/lazy/telescope.nvim/lua/telescope/builtin/__lsp.lua:364 /Users/work/.local/share/nvim/lazy/telescope.nvim/lua/telescope/builtin/__lsp.lua:400 /Users/work/.local/share/nvim/lazy/telescope.nvim/lua/telescope/builtin/init.lua:543 /Users/work/.local/share/nvim/lazy/telescope.nvim/lua/telescope/command.lua:188 /Users/work/.local/share/nvim/lazy/telescope.nvim/lua/telescope/command.lua:259 /Users/work/.local/share/nvim/lazy/telescope.nvim/plugin/telescope.lua:108

~

• WARNING vim.lsp.util.jump_to_location is deprecated. Feature will be removed in Nvim 0.12
  • ADVICE:
    • stack traceback: /Users/work/.local/share/nvim/lazy/telescope.nvim/lua/telescope/builtin/__lsp.lua:187 /opt/homebrew/Cellar/neovim/0.11.0/share/nvim/runtime/lua/vim/lsp/client.lua:679 vim/_editor.lua:0

Neovim version

NVIM v0.11.0
Build type: Release
LuaJIT 2.1.1744318430

Operating system and version

macOS 15.4.1

Telescope version / branch / rev

telescope 0.1.8

checkhealth telescope

==============================================================================
telescope:                                 require("telescope.health").check()

Checking for required plugins ~
- OK plenary installed.
- OK nvim-treesitter installed.

Checking external dependencies ~
- OK rg: found ripgrep 14.1.1
- OK fd: found fd 10.2.0

===== Installed extensions ===== ~

Telescope Extension: `session-lens` ~
- No healthcheck provided

Steps to reproduce

:Telescope lsp_definitions

Expected behavior

No response

Actual behavior

vim.lsp.util.jump_to_location is deprecated. Run ":checkhealth vim.deprecated" for more information

Minimal config

local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs { "config", "data", "state", "cache" } do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.uv.fs_stat(lazypath) then
  vim.fn.system {
    "git",
    "clone",
    "--filter=blob:none",
    "https://github.com/folke/lazy.nvim.git",
    lazypath,
  }
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  {
    "nvim-telescope/telescope.nvim",
    dependencies = {
      "nvim-lua/plenary.nvim",
    },
    config = function()
      -- ADD INIT.LUA SETTINGS THAT ARE _NECESSARY_ FOR REPRODUCING THE ISSUE
      require("telescope").setup {}
    end,
  },
}

require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

[jamestrew]

I think this issue is resolved on the master branch. I don't have the ability to push new releases so until someone who can does, the 0.1.x branch and releases of telescope can be considered loosely broken.

[nwehrlich]

Came here to report this, because I saw that vim.lsp.util.jump_to_location wasn't used at all in master. Thought I was going crazy.

[haug1]

Looks like this was fixed on the master branch in October, would love to see a new release soon :pray:

[carbolymer]

@Conni2461 There hasn't been a release for over a year, is there a chance for one soon?

[moeezali2375]

Is this issue resolved or what ?

[barbosa46]

Is this issue resolved or what ?

A quick fix is to change the "branch" field in your plugin manager from "0.1.x" to "master". For example, in Lazy:

{
    'nvim-telescope/telescope.nvim',  branch = 'master',
      dependencies = { 'nvim-lua/plenary.nvim' }
    }

I believe this can lead to more bugs, since you're cloning the master branch, but while we are waiting for a release, it might help :)

[pmthexton]

I believe this can lead to more bugs, since you're cloning the master branch, but while we are waiting for a release, it might help :)

Yeah. I was worried about bringing other "don't want that" stuff in as things develop in master as well.

Happy to report that with Lazy at least (I don't know other package managers), you can do sha pinning. So I've chosen the current tip of master to bring in directly.

{ 'nvim-telescope/telescope.nvim', -- branch = '0.1.x', commit = 'b4da76be54691e854d3e0e02c36b0245f945c2c7', }

[alecandido]

Apparently, there has been a release three days ago. Is it working for you?

[krishna4040]

is it fixed in the latest 0.1.9 release? PS: I see a merged PR in the release #2478 that fixed this but when i try to clone the 0.1.9 release it fails, and when cloning the 0.1.x branch it is still at the previous release? can someone let me know how do i upgrade?

[wroever]

can someone let me know how do i upgrade?

Here's what I learned digging into this:

lazy.nvim encodes default package versions in a static repository file that is updated with each lazy.nvim release. So until lazy.nvim gets a new release, it will install v0.1.8 of telescope.nvim by default.

You can override the target package version using the version property as per the lazy.nvim docs here, which IIUC causes Lazy to pull the latest matching package version via LuaRocks, ensuring you get an official release. I set this to ^0.1.9 and added a TODO in my config file to flag mentioning that the version property can be deleted once a new lazy.nvim release is available.

As other folks here have noted, you can alternatively specify a branch or commit, but using version seemed like the safer approach to me since (IIUC) it guarantees you get a released version of telescope.nvim.

[5ur]

Change to tag in your return if you had branch like me. Ref: release v0.2.0