Improve documentation generation during release process
Since the switch to Meson, the API documentation is not generated and distributed in the source tarball. This is great (putting generated stuff in tarballs makes for non-reproducible tarballs, and makes them bigger than they could be), but it does mean that the scripts which update developer.gnome.org can’t extract the documentation from new releases and upload it automatically.
Currently, a maintainer has to locally generate the documentation as a separate tarball (after release) and upload it to developer.gnome.org manually. This is easily forgotten, boring, and not scalable.
We could add a CI job which generates the documentation for a release tag and uploads it.