Hey all,
Just a quick little update, the developer for yay got back to me and had this to say:
Github Explanation from Jguer - developer
yay -Y --gendbcreates the file~/.cache/yay/vcs.jsonwith the latest SHA of the origin for each-gitpackage. It gives a starting point foryayto start checking devel upgrades. At this point foryayit does think that you have the latest upstream version installed (even if you do not).When you run
yay -Syu --devel, yay checks again all of the remote SHAs against~/.cache/yay/vcs.jsonand proposes the package for upgrade if they differ.Hopefully if you use yay on a regular basis once the upstream SHA of a -git package has changed, it will be proposed by yay, youâll install it and yay will update its entry in
~/.cache/yay/vcs.json.Itâs a matter of eventual consistency so
yay -Y --gendbjust tells yay to assume all those-gitpackages have their latest version installed.
So what does this mean exactly? Well, essentially the tl;dr is after the first time that yay -Y --gendb is run, anything after that then yay will see the git update, but since I just did it for the first time today, everything looks up to date. So essentially the next time that popsicle-git has an update, that is when yay will for sure see the update.
A little bit confusing at first to not know that, but thatâs more or less how yay operates by design so I wouldnât say this is a bug/issue. For myself Iâll just update popsicle-git through Pamac for now and the next time popsicle-git gets an update, yay should be able to see it the next time when it compares it to itâs own database. Time will tell! Hope this is helpful to yâall and hope everyone has a great weekend 
