i recall it needing a "valagen" bin i believe. maybe check if something else brought it into your system, as this system's fairly fresh. or ofc it's possible i got confused, and commented on the wrong tab :) ty

The following two changes need to be made to the PKGBUILD in order for this package to work properly with AUR helpers like yay:

Line 7: pkgver=5.16.4, NOT 5.15.6

Line 19: Typo: underscore missing from source=("https://download.kde.org/stable/plasma/$pkgver/$_pkgname-$pkgver.tar.xz"{,.sig}) results in attempt to download discover-snap-$pkgver.tar.xz which does not exist on the KDE servers

Apparently git push isn't allowed on the AUR because if it was I would have a fix and a pull request waiting for you.

@michaldybczak
AUR isn't for people who don't know basic bash and aren't willing to learn. Anyone can upload whatever they want to it and maintainers change all the time. At least be able to read it once and check the diff on new versions.

I'm just an average user and don't have enough technical knowledge to update the PKGBUILD to the current version myself. I thought the reason for such packages is that we - average users - could install it easily and keep it up to date. If that package is just a blueprint and must be maintained manually, this is too much of a hassle for me.

This package is either dead or poorly maintained. There were no regular updates in the past and we had to ask for the newer version. Now even this doesn't help and the package is at least outdated since 2 months.
Maybe there is a way to use git version and compile it with snap? Hmm... I'll try.