Wrong version displayed for msprime

[jeromekelleher]

The wrong version of msprime is being displayed on the intro page. For some reason, we've got version = "0.1.dev1", which means that either the custom sphinx extension defined in tskit-dev/msprime#1408 isn't being executed, or the sphinx config is somehow being overwritten later in the process.

The Python path must be OK, because we wouldn't get the autodocs output otherwise.

Any ideas @benjeffery?

[benjeffery]

Odd, I can't recreate locally. I think we should use a more flexible way of getting the version number in anyway as I suggested over at tskit-dev/msprime#1396 (comment)

[jeromekelleher]

Happy to look at alternatives to setting the version via sphinx.

[jeromekelleher]

Maybe it's an issue with running in a venv? But, you always run everything in venvs, don't you? (So you should see it locally if so...)

[benjeffery]

Yes, I'm always in a venv, I even wiped my venv and pip installed the CI-docs requirements, still couldn't recreate.

[jeromekelleher]

Weird. A snippet of JS would be more flexible, allright, if we could do that.

[jeromekelleher]

Looks like this is a problem with shallow clones done on Actions:

• Wrong reported version, while running under actions/checkout@v2 pypa/setuptools-scm#414
• setuptools_scm incompatible with default actions/checkout@v2 pypa/setuptools-scm#480

I'll try the fetch-depth: 0 fix and see how it goes.