It's the same reason packages like 'google-chrome-beta' [1] and 'google-chrome-dev' [2] exist, it's just so users can use more cutting-edge releases if they so choose. I just use '-beta' and '-alpha' as my version of the '-beta' and '-dev' versions, they're all part of my actual program's Git repository, they're just named such to describe the nature of the release.
I could see the possible confusion with it being thought that these were prerelease-like versions that are just temporary codenames that'll be obsoleted by new ones in the future, but again, this could easily have been seen by looking at the PKGBUILDs, and equally as important at the upstream repository [3].
Again, I'm not trying to create a bunch of drama, I'm just really wanting to know how this deletion could have even been submitted if everything was properly checked, as this becomes quite an issue when I'm wanting these packages to be reliably available to end users.
[1]: https://aur.archlinux.org/packages/google-chrome-beta/
[2]: https://aur.archlinux.org/packages/google-chrome-dev/
[3]: https://github.com/makedeb/makedeb/branches
---
Hunter Wittenborn
mailto:hunter@hunterwittenborn.com
https://www.hunterwittenborn.com
https://github.com/hwittenborn
---- On Thu, 16 Dec 2021 18:52:50 -0600 Kevin Morris via aur-general