Git tagging nimble package repo with "0.5.0" instead of "v0.5.0" caused a random package version to get fetched
The [parsetoml][1] .nimble file has this version string: [`version = "0.5.0"`][4].

When that version got updated in the .nimble file, git tag **0.5.0** (without "v" prefix) got applied to it. That caused `nimble install` from within the repo dir on Travis to fetch a 0.3.2 version of parsetoml:

>  Verifying dependencies for parsetoml@0.3.2

[travis log][2]

The interesting piece is that a version 0.3.2 has never been git-tagged, but that "version" string in .nimble was last set to "0.3.2" back in May 2018 (https://github.com/NimParsers/parsetoml/commit/17c6c5103b5e0c56946908fa57e9ca2e2c9712f0).

---

That caused other issue like failing to find a nimble task that was actually being defined in the `parsetoml.nimble` file.

See the messages on IRC describing this confusion: https://irclogs.nim-lang.org/10-06-2019.html#17:20:09

---

By fluke, I thought of removing the **0.5.0** and retagging it with **v0.5.0**, and it worked!

Now `nimble install` fetched the correct version ([see travis log][3]) and there's no false failure related to not finding the `run_toml_tests` task.

---

Can this behavior be explained?

## `nimble` version
```
nimble v0.10.2 compiled at 2019-06-10 13:40:01
git hash: d15c8530cb7480ce39ffa85a2dd9819d2d4fc645
```

## `nim` version
```
Nim Compiler Version 0.20.99 [Linux: amd64]
Compiled at 2019-06-10
Copyright (c) 2006-2019 by Andreas Rumpf

git hash: 485b008433ba8e96c572f30925eebdea45bb6d92
active boot switches: -d:release
```

[1]: https://github.com/NimParsers/parsetoml
[2]: https://travis-ci.org/NimParsers/parsetoml/builds/543805185#L1351
[3]: https://travis-ci.org/NimParsers/parsetoml/builds/543840143#L1360
[4]: https://github.com/NimParsers/parsetoml/blob/329cc618fe27a6c89708d1fa17ddc72f8da97e08/parsetoml.nimble#L3