You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Stable is "stable" and generally what gets used by distro maintainers, what you download by default from pip, etc.
master/main is the latest development version which has new changes not in stable. check the version of your local beets and use the corresponding changelog.
True but unrelated.
2.0.0 is an actual release that exists (i.e. stable) and the official documentation website should reflect that. This is independent of whether the changelog file I referenced is on the master branch or not (or rather, it depends on how the docs are deployed on a technical level, which is not what I'm commenting on). There is also a changelog on GitHub's releases page, which the above link points to.
Maybe the stable branch on the website has a manual trigger? I'm not sure why it didn't get updated. Or moving from 1.x to 2.x is not expected by the deploy scripts.
Problem
The changelog on https://beets.readthedocs.io/en/stable/changelog.html does not list 2.0.0 as the latest release, even though I can see in https://github.com/beetbox/beets/blob/master/docs/changelog.rst that there is a changelog for 2.0.0.
Is the docs deployment outdated or is this not the correct location for the docs? It's what I found in the sidebar of https://beets.io/
The text was updated successfully, but these errors were encountered: