From: #1300 (comment)
Because of the way the kedro-plugins repository is organized, with multiple projects living inside it, each with their own releases, ReadTheDocs will not automatically generate a stable branch for kedro-datasets.
This would require us to manually update the latest version on the deindex-old-docs.js script for each new kedro-datasets release.
Could we find a way to set up this stable branch for kedro-datasets? Either through ReadTheDocs' automation rules or, failing that, maybe by setting a stable branch on the repo itself and using it on ReadTheDocs?