First, let me say thank you for the great job you are doing with this project.
As I'm sure you're aware, many plugin managers (e.g. lazy.nvim) can be configured to only update plugins once a new version is released. In this particular case, I think it could be beneficial for the project to make sure that both the most recent release of the main repo (neorg) and this one are compatible with one another.
For example, currently, my local plugin version of nvim-neorg is at v5.0.0 whereas neorg-telescope is at d803ae4. Without further user interaction, this breaks neorg-telescope (due to neorg@5706f1e, I assume). In the future, this could be prevented by releasing new versions "simultaneously" (or close to it).
Hey all,
First, let me say thank you for the great job you are doing with this project.
As I'm sure you're aware, many plugin managers (e.g. lazy.nvim) can be configured to only update plugins once a new version is released. In this particular case, I think it could be beneficial for the project to make sure that both the most recent release of the main repo (
neorg
) and this one are compatible with one another.For example, currently, my local plugin version of
nvim-neorg
is atv5.0.0
whereasneorg-telescope
is at d803ae4. Without further user interaction, this breaksneorg-telescope
(due toneorg@5706f1e
, I assume). In the future, this could be prevented by releasing new versions "simultaneously" (or close to it).Thank you for your time & consideration :smile: