ansible-galaxy still installs v1.1.1 about docker.ubuntu HOT 5 CLOSED

Not sure why it's doing this, but it is. I've manually updated in Galaxy several times to no effect.

In the meantime, let's assume the best installation method is to install from git:

ansible-galaxy install git+https://github.com/angstwad/docker.ubuntu

from docker.ubuntu.

I suspect it is due to the fact that ansible-galaxy takes latest version based on alphabetical order, exactly like Github tags are sorted.

from docker.ubuntu.

I believe @luka5z is correct. The tags need to be consistent; that is, it should be published as "v1.1.5" instead of "1.1.5"

$ python
Python 2.7.11 (default, Jan 22 2016, 08:29:18)
[GCC 4.2.1 Compatible Apple LLVM 7.0.2 (clang-700.1.81)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> 'v1.1.1' > '1.1.5'
True
>>> 'v' > '1'
True
>>>

In the meantime, users can explicitly specify the version to get the latest, after manually looking up what the latest version is.

ansible-galaxy install angstwad.docker_ubuntu,1.1.5

from docker.ubuntu.

This is fixed with the v1.1.6 and I'll get around to re-tagging in the future sometime.

from docker.ubuntu.

This is resolved now.

I'll note that from the discussion in this Stack Overflow question, as well as this Stack Overflow question about the v-prefix. While using a v-prefix for VCS tags is accepted (see SemVerTag on SemVer 1.0.0), in SemVer 2.0.0, that recommendation was removed. This is touched on in the FAQ of a yet unreleased version of SemVer spec.

So docker.ubuntu should get released without v prefixes, but if you want to use v-prefixes in your Git tags, that's okay, but an outdated practice.

Technically you were doing the right thing by making releases without the v-prefix. You'll have to correct the old release versions to drop the v-prefix to get ansible-galaxy to cooperate with you, though.

from docker.ubuntu.