Supporting version tags with "v" at the beginning

[macintacos]

Hello!

Would it be possible to subtly allow for "v" to be searched for when specifying a version? For example, bufferline.nvim and legendary.nvim follow semver in their release tags, but they prepend "v" to the beginning. These don't seem to be picked up when I specify something like ^3.0.0 for bufferline, for example - lazy.nvim seems to fallback to just looking at the latest commit in the main branch, since I don't see it updated in lazy-lock.json.

I figure, it's easier to search for that in lazy.nvim itself, rather than get every project under the sun to adopt "strict numbered versions" in their release tagging - I find vX.Y.Z to be a common release tagging mechanism for many projects. I also figure it's better for lazy.nvim to support this, as it is more geared towards "do what I mean" configuration

[folke]

version already supports that, so how do you specify the version?

[folke]

{
  "akinsho/nvim-bufferline.lua",
  event = "BufAdd",
  version = "^3.0.0",
}

[macintacos]

Ah, maybe I'm misunderstanding. When I look at the UI, I see what you see, however in lazy-lock.json, I see branch = "main":

  "bufferline.nvim": { "branch": "main", "commit": "028a87933d99f8bb88f2f70a4def3ff9574f3594" },

I see some other plugins where I've specified the version (like neo-tree) and in the lazy-lock.json the value for branch matches what I would've thought, but as the name implies, it's probably literally talking about the branch and isn't a catchcall term.

Perhaps the lazy-lock.json should also note what tag is being used?

[folke]

the tag is not needed to save in the lockfile. The only thing you need is the commit and the branch where that commit is on. Tags are just refs to commits on certain branches

[macintacos]

Alrighty then - I'll just try to not look at the lazy-lock.json, as it can confuse me a bit when comparing the two, and will just use the UI instead to double-check things - thanks!

[folke]

When downgrading, the ui, showed the plugin to be downgraded under loaded. Just pushed an update with a new section updates. That's probably what confused you