today the update to pacman 7.0.0-r3 was installed on my machine through the core-testing repository. I am usually using the AUR helper yay for any kind of updates. After the update, yay didn't start anymore, as the library version of libalpm increased to 15 and yay was still looking for 14. A manual rebuild of yay easily fixed this.
that's a common and expected behaviour - packages like yay, installed locally from AUR (basically your own private binary repo) will never be in-sync with Arch package repositories.
However, I am wondering if there is any way how to make such an update smoother, so that yay would be rebuilt in the same step after pacman was updated and avoid the necessity for a manual rebuild?
as things stand now, not easily, perhaps you can edit your yay PKGBUILD to have a depends on "libalpm.so=14" so that pacman will warn you that updating the library will break the package. but then you'd still need to fix things manually. -- damjan