Hmmm I believe it would be good to update the packages by xbps and run the migration and other stuff manually.
But if there are no tagged releases I guess it cannot be included in main repo?
Is there any information on why pkgs cannot be based on a commit-hash?
Because commit hashes are often intermediate quality software, not deemed worthy of a release by upstream. Also because people keep bothering maintainers to update to the next day or week's commit hash, and it uses our time when we already have things to do to maintain Void.
Also note: Flask is a utility for Python. It is system level. flaskbb uses Flask to do things. That's why we package Flask: it has a variety of uses and knows exactly what it can or can not control within a system. (Flask gets installed to a few directories, and just sits there. it doesn't require other programs be installed and then try to change their configurations before being usable.) I've heard a recommendation to use Ansible Galaxy to set up things like flaskbb, just in case that's of interest to you.