Why latest docs points to docs from main branch and not latest released version?

[macieyng]

I was trying to configure bandit with pyproject.toml for sometime and bandit was unable to read the config. I checked the versions: I'm using (1.7.4) which is latest/recent, so the docs seems to be fine. But then I switched docs to 1.7.4 and boom - completely different page showed up.

LATEST - https://bandit.readthedocs.io/en/latest/config.html#bandit-settings
1.7.4 - https://bandit.readthedocs.io/en/1.7.4/config.html

So the question I want to ask is: Why latest docs points to docs from main branch and not latest released version?

But also: When new version is scheduled to be published? Can we expect some kind of rc or alpha?

Thanks guys!

[TobKed]

Acutally it is working as it is written in the Read The Docs documentation:

Read the Docs: Versioned Documentation

Read the Docs supports multiple versions of your repository. On initial import, we will create a latest version. This will point at the default branch defined in your VCS control (by default, main on Git and default in Mercurial).

In the normal case, the latest version will always point to the most up to date development code. If you develop on a branch that is different than the default for your VCS, you should set the Default Branch to that branch.

Which makes sense in my opinion. Latest does not mean latest stable or latest release.