We cannot automatically build and host this package's documentation on release, because the documentation is currently hosted on the main bloomberg/blazingmq repository. This means that every time we update the documentation for this package, we have to manually file a PR against that repository, have it reviewed, and have it merged into the main repo. The process would be much simpler if we instead build and deploy the documentation within our GitHub Actions workflow on each release, publishing to our own repo's GitHub pages.
We cannot automatically build and host this package's documentation on release, because the documentation is currently hosted on the main bloomberg/blazingmq repository. This means that every time we update the documentation for this package, we have to manually file a PR against that repository, have it reviewed, and have it merged into the main repo. The process would be much simpler if we instead build and deploy the documentation within our GitHub Actions workflow on each release, publishing to our own repo's GitHub pages.