Wrong `parcels.__version__` number in v4-alpha release

[erikvansebille]

Parcels version

0.1.dev1 (but should be v4-alpha)

Description

Following on from #2259, the upload of the v4-alpha package to conda is fine, but the actual parcels.__version__ number is wrong:

Code sample

import parcels
print(parcels.__version__)

0.1.dev1

[VeckoTheGecko]

We use setuptools_scm (which looks at the git tags to determine the version) to pick up the version information for the project.

I think this is something that is pretty much unavoidable unless we have this manually defined in a file in the repo - which I don't think is worth the change

[erikvansebille]

OK, but will the version number be correct once we start doing 'real' releases of v4? Because once we have a proper v4 release (alpha, beta or stable), we would want to have the parcels.__version__ number be correct?

[VeckoTheGecko]

but will the version number be correct once we start doing 'real' releases of v4

Yes, our release cycle and version finding has not changed from version 3

Once we do an official beta release (i.e., make a tag on GitHub, publish a release, make available on conda-forge) we will see corrent version information