v2018.10.13 tag points to wrong version

[nijave]

Issue description

git clone https://github.com/pypa/pipenv.git
cd pipenv
git checkout v2018.10.13
cat pipenv/__version__.py

Expected result

#     ___     ( )  ___      ___       __
#   //   ) ) / / //   ) ) //___) ) //   ) ) ||  / /
#  //___/ / / / //___/ / //       //   / /  || / /
# //       / / //       ((____   //   / /   ||/ /
__version__ = "2018.10.13"

Actual result

#     ___     ( )  ___      ___       __
#   //   ) ) / / //   ) ) //___) ) //   ) ) ||  / /
#  //___/ / / / //___/ / //       //   / /  || / /
# //       / / //       ((____   //   / /   ||/ /
__version__ = "2018.10.14.dev0"

Steps to replicate

clone repo
checkout v2018.10.13 tag
check version file

Looks like the v2018.10.13 tag is attached to the wrong commit. The v2018.10.9 tag appears correct. This makes it difficult to build this specific version

[techalchemy]

It was tagged late while I was on vacation, it is identical in every other way.

[nijave]

Issue is I'm trying to automatically build a wheel and checking out v2018.10.13 and building results in a wheel with the wrong version in the name so I'd need to put a manual workaround in place to fix that specific version

I am trying to workaround this Artifactory bug https://www.jfrog.com/jira/browse/RTFACT-16189

[techalchemy]

Ah ok I can push the right tag in a bit, apologies. The only difference is the version in the version file I just tagged out of order because I was on vacation / not using my normal tooling

[nijave]

Awesome, thanks!

[homocomputeris]

@techalchemy 2018.11.26 also has a wrong version:

pipenv/pipenv/__version__.py

Line 5 in 742ae1b

__version__ = "2018.11.15.dev0"

So, when installed from GitHub, not PyPI, it gives:

$ pipenv --version
pipenv, version 2018.11.15.dev0

[homocomputeris]

#3326 seem to be more or less the same