I maintain neovim in EPEL, and previously just rebased to the version shipped in Fedora periodically. Some of our internal users use plugins that might depend on the latest and greatest release, so they basically get blocked if neovim falls behind.

It has been brought to my attention that neovim can and does deprecate APIs in minor releases; e.g.:

https://github.com/neovim/neovim/blob/master/runtime/doc/deprecated.txt

(In theory... diffing between minor release tags from a git checkout, things seem to get added to this but not removed; in practice some users have had to adjust their configuration)

Several questions:
- does a new neovim minor release count as an 'incompatible upgrade' then?
- or does this only count if dependent packages are broken? (Right now we don't package additional plugins, ergo no packages get broken by updates)
- if this is considered incompatible, can we get an exemption for neovim? Or more broadly for pre-1.x software

Additional context: I'm trying to delegate this package to someone who uses it more, but we want to figure out first if it's easier to maintain it in EPEL or in the CentOS Hyperscale SIG