The version release workflow added in #87 had a few issues, which are all fixed in this PR:
the step to create the git tag did not check out the repository, nor did it configure the git credentials properly
the same version string was used for both tagging and building the docs, while we currently use the vX.Y.Z format for the tag and X.Y.Z for the docs version
the doc building step did not specify a dependency on the tagging step, which meant it would run and publish the docs even if tagging was not successful
The version release workflow added in #87 had a few issues, which are all fixed in this PR:
vX.Y.Z
format for the tag andX.Y.Z
for the docs version