Replies: 2 comments 4 replies
-
For the stable branch, it is very important. It's also impossible to tell when a breaking change will be introduced. For example barbar.nvim one day suddenly started crashing lvim because a PR was merged without being tested. It's a lot of fires to put out, but you're absolutely right, on my own branch I've been keeping nvim-cmp up to date because of some nice behavior improvements but I haven't pushed for updates in LunarVim because it's tedious to get approval. What we could do is export |
Beta Was this translation helpful? Give feedback.
-
I agree with pinning some plugins which often introduce breaking changes, such as NvimTree
But it's worth it to pin every single core plugin? That causes some annoyances, especially when there are important updates: users have to make a PR to update commit or wait for the pin to be updated. For example
Comment.nvim
received an important update recently; it introduced integration with treesitter for commenting, but I can't update it due to the pin.Also having 30~40 core plugins makes it difficult to keep everything updated.
At least it'd be better to make commits customizable, using something like
lvim.plugins_commit
Beta Was this translation helpful? Give feedback.
All reactions