You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the exsiting issues of the plugin I have a problem with
Neovim version (nvim -v)
NVIM v0.8.1
Operating system/version
MacOS 12.8
Describe the bug
I am using { 'folke/lazy.nvim', tag = 'stable' } as a temporary workaround for #260. This morning when I did :Lazy update, it did not update to the latest stable version v7.7.0 (cba99de). Doing a git log in ~/.local/share/nvim/lazy/lazy.nvim, I observed that while the latest cba99de commit is present in the tree, the stable tag had not been updated. I suspect the cause is related to the following:
require("lazy").setup({
{ 'folke/lazy.nvim', tag = 'stable' },
})
Expected Behavior
I would expect setting tag = stable in the config would result in the tag being updated when it changes in the plugin repo, and hence the plugin updating to what is now stable.
Repro
No response
The text was updated successfully, but these errors were encountered:
The problem is that the stable tag for lazy gets updated after every release.
Lazy would not do an update when tag=stable, since the local repo would already be on stable.
Did you check docs and existing issues?
Neovim version (nvim -v)
NVIM v0.8.1
Operating system/version
MacOS 12.8
Describe the bug
I am using
{ 'folke/lazy.nvim', tag = 'stable' }
as a temporary workaround for #260. This morning when I did:Lazy update
, it did not update to the latest stable version v7.7.0 (cba99de). Doing agit log
in~/.local/share/nvim/lazy/lazy.nvim
, I observed that while the latest cba99de commit is present in the tree, thestable
tag had not been updated. I suspect the cause is related to the following:Steps To Reproduce
Expected Behavior
I would expect setting
tag = stable
in the config would result in the tag being updated when it changes in the plugin repo, and hence the plugin updating to what is nowstable
.Repro
No response
The text was updated successfully, but these errors were encountered: