That's assuming you do system upgrades through paru/yay. However, you may not want to upgrade the packages you've obtained from the AUR and so you upgrade using pacman. That may cause the updated libalpm to become incompatible with the installed yay/paru.

▲

nicce 6 hours ago | parent [-]

yay used to be in the official Arch Linux repository for some time, wonder why it was removed.

	▲	morserer 6 hours ago \| parent \| next [-]
		Iirc it was to force the extra step necessary for the user to acknowledge that the AUR can bootstrap malware if used blindly. This seems to be a relatively consistent discussion surrounding AUR helper development; for example, adding UX to incentivise users to read PKGBUILDs, lest the AUR becomes an attractive vector for skids. No one wants the AUR to become NPM, and the thing that will incentivise that is uneducated users. Having the small barrier of not having helpers in the main repos is an effective way of accomplishing that.
	▲	Levitating 5 hours ago \| parent \| prev [-]
		https://wiki.archlinux.org/title/AUR_helpers AUR helpers like yay are not supported officially. The other commenter sheds some light as to why.