Stable gets badly out of date #367
Description
It looks like the "stable" version of the docs is being used by some in the community, even though we link to "latest" and I think that is the default.
The workflow seems to be that a new tag/release needs to be created, and then the next time a PR triggers a doc rebuild, stable will use the contents of that release. Probably having something automated to create a new stable each month (maybe only if there have been commits in that month) would be best, as "stable" was extremely stale (2024) before I created a new tag today.