Replies: 2 comments 6 replies
-
|
That is not normal. Also setting version to Does lazy.nvim update now properly? Maybe updating lazy was broken in that version for some reason |
Beta Was this translation helpful? Give feedback.
6 replies
-
|
Closing the discussion as my issue seems to be resolved now |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hey everyone,
After using
lazy.nvimfor months (basically since it was released), today I was SHOCKED to see something.From
LazyVimrelease notes, I saw it mentionedlazy.nvimnow supportsminiplugins by default, so I updated my config, and, well, it doesn't work as expected.Tried debugging the issue and saw that my
lazy.nvimis stock at version9.14.2, which is super old (I update my plugins at least once a day)I set up
lazy.nvimsimilar toLazyVimstarter:And I had these for the defaults:
I thought it's because
version = false, so I changed it toversion = '*'.A LOT of my plugins were updated after using
*(didn't know that either 🙁 ), but no matter what I did, the only way I could makelazy.nvimbe updated was by removing its directory, forcing a newclone.What am I missing here? Why wasn't/isn't
lazy.nvimupdated?Beta Was this translation helpful? Give feedback.
All reactions