Hi, so I actually was able to figure this out in around a minute.
What’s happening here is that there’s double listings inside the CachyOS repos for certain packages. One of them has the wrong release number.
In my case it was this right here:
As you can see, the cachyos repo has a pacman-contrib package that has a different release number than the rest.
Shelly is picking this up and deciding it needs an update, because they share a name, although that’s not the repo the user has that package installed from.
So, it’s actually working as intended. It’s informing the user of an upgrade to an existing package from a different repo they have available. They should still communicate that it’s a repo change though, which is the actual issue here.
The idea is the same for Flatpaks, if you have multiple repos Shelly is going to say there’s a newer version somewhere, even if you don’t need it for your current setup.
Ditto to the AUR, which is why it will show that you have potential upgrades from there even if you don’t have those packages installed from the AUR.