Missing/incoherent git tags

[streino]

Master was recently bumped to version 1.2.0, could you please push the v1.1.0 tag?
The v1.0.3 tag also seems incorrect, pointing to a v1.1.0 commit.

[smotornyuk]

There is a small discrepancy between the version in the setup.py and the actual version of the extension. Now it's correct, but in the case of v1.0.3 ignore v1.1.0 in the source. Basically, git tags are the source of truth

PS
v1.1.0 and v1.2.0 tags added to the repo

[streino]

Thanks!
I'm a bit confused about v1.2.0: the tag is there but it's still that version on master. How does it work? You only bump the version right before setting the tag?

[smotornyuk]

Yes. Unfortunately, the author of this extension is not working with CKAN at the moment, so some chores are not done correctly. We are working on release management recommendations and automatization for CKAN extensions, which should solve the problem in most cases. But at the moment the main focus is on CKAN core and some significant improvements for it and I can't say when exactly the problem is going to be solved:(