I'm not sure what happened, but the docs workflow was never triggered for the tag v0.1.0, so the stable docs currently links to v0.0.0.
Looking at your Actions tab, TagBot seemed to run fine but the creation of the tag didn't seem to trigger the docs workflow. Usually this suggests that TagBot wasn't given an ssh key (because an ssh key is needed for workflows to trigger other workflows). Naturally I can't verify this though since I don't have access to your repository secrets. Also v0.0.0 built fine so that doesn't seem like a likely culprit anyway... If you already had it though it might well just have been a GitHub outage? Previously when I ran into this sort of situation I'd just release a new patch that contained nothing, just to trigger the docs build.
I'm not sure what happened, but the docs workflow was never triggered for the tag v0.1.0, so the stable docs currently links to v0.0.0.
Looking at your Actions tab, TagBot seemed to run fine but the creation of the tag didn't seem to trigger the docs workflow. Usually this suggests that TagBot wasn't given an ssh key (because an ssh key is needed for workflows to trigger other workflows). Naturally I can't verify this though since I don't have access to your repository secrets. Also v0.0.0 built fine so that doesn't seem like a likely culprit anyway... If you already had it though it might well just have been a GitHub outage? Previously when I ran into this sort of situation I'd just release a new patch that contained nothing, just to trigger the docs build.