npins updates?

[ckoehler]

Hello!

Looks like npins can automatically track branches to update pins automatically. Is that done anywhere? I checked the Workflows in the repo and nothing looks like it would update the pins, but maybe it's somewhere buried in a flake update or something?

[NotAShelf]

I avoid unattended updates to avoid breaking main without anyone noticing. If a specific plugin you need is outdated, I can push a quick version bump for that. Though I have also been considering an automatic updater for a while now, perhaps bimonthly to make sure plugins stay up to date.

[ckoehler]

There isn't right now, but I noticed that nixpkgs' vim plugins do seem to get updated automatically, so I was going to favor pulling them from there instead of npins here.

Bimonthly sounds fine, or maybe weekly? If there were a bot to do that via PR, you'd still have a way to manually update them with minimal work.

[NotAShelf]

The main "problem" is that we do not have any tests set up yet. It's been on my to-do list for a while (see: #285) but I could not find a comprehensive testing mechanism that can ensure the plugin updates don't break anything. I also don't have the means to test every updated plugin every single week, so we increase the chances of merging breakage in case of automated updates.

If we can figure out a way to test each plugin in CI, then automated updates should be easy to manage and I'll feel better about auto-updating plugins.

[ckoehler]

I don’t think there is such a thing. Creating a config for each plugin, loading it with nvim -u (and maybe a command), and making sure there are no errors might work.

Trying to decide which I mind more, having to manually bump outdated plugins, or having my config break on update. I already deal with the latter using lazy.nvim and updating every few weeks I guess. 🤔 Curious to hear other opinions.