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
As the title says, whenever a plugin dependency gets updated through :Rocks update, it is added as a new entry to the rocks.toml entry, causing some unexpected junk entries.
This one is a bit more hard to reproduce so I cannot really give reliable reproduction steps here, hope it's not a blocker!
The text was updated successfully, but these errors were encountered:
NTBBloodbath
changed the title
[Bug] Plugins dependencies added to rocks.toml when updated
[Bug] Plugin dependencies added to rocks.toml when updated
Feb 11, 2024
Uhh one example could be nvim-nio which recently got an update and it's one of our dependencies.
The rocks.toml looks something like this after running :Rocks update:
[plugins]
# .....nvim-nio = "1.6.0"
If you remove the newly added nvim-nio entry nothing happens, so it's not something that can be reproduced over and over again so I guess testing will be hard for this one 🫠
As the title says, whenever a plugin dependency gets updated through
:Rocks update
, it is added as a new entry to therocks.toml
entry, causing some unexpected junk entries.This one is a bit more hard to reproduce so I cannot really give reliable reproduction steps here, hope it's not a blocker!
The text was updated successfully, but these errors were encountered: