Have you checked for existing feature requests?

• Completed

Summary

New deployments of the docs are still showing the API documentation from 1.114.0. I vaguely understand how to fix this — pulsar and the other documentation sources are submodules, and once they're updated we can run the script to regenerate the docs — but it would be great if this could be automated.

What benefits does this feature provide?

Instead of our having to remember it (and open a PR and get someone to review it), we could make it the last step of our release automation.

Any alternatives?

Doing it manually! Which sucks.

Other examples:

This is a bit tricky because I believe it would involve a GitHub action that runs a script, then commits the new files back to the repo. But I'm pretty sure there's prior art for this somewhere.