...
The Github release creation process creates a tag on the main branch in the Git repository and a Github release that will trigger the build of the new documentation version on Besu Read The Docs project.
...
Read The Docs (RTD) will generate the following versions when a new tag is detected on the repository main branch:
- Latest: corresponds to the latest commit in the master main branch of the doc repos
- CalVer version (for example: "21.1.4"): corresponds to the tag in the master tat on the main branch that was created during the release
- Stable: corresponds to the last created tag on the main branch (for example 21.1.4)
When creating a release, RTD will build 3 versions : latest, CalVer version and stable and they will all show the same content from the same commit.
But then when contributors will continue to work on the doc, the latest will be rebuilt from the latest master main commit each time a new PR is merged and the CalVer version and stable will be behind latest.
Read The Docs version automatic activation
By default, new doc CalVer version are not activated by RTD, but we have a setup that tells RTD RTD is setup to activate CalVer numbered versions automatically once built: https://readthedocs.org/dashboard/hyperledger-besu/rules/
You can check the history of activations on this page as a maintainer.
NOTE: Besu doc repository default branch is now named main.