Update to Version Tagging
georgenalen opened this issue · comments
Hello,
I wanted to give an update on a tagging change that will take place on the next release, scheduled at some point in May. Without realizing that Ansible Galaxy needs version numbers in the Semantic format that excludes the preceding “v”, for example 1.2.1 vs v1.2., we have been using tags with the preceding v. This has caused our galaxy space to not update with our latest releases.
The plan going forward we plan to adjust the version number formatting on the first release for each repo in May. Please make note that if you are relying on release tags to keep up with latest versions, the numbering format will change. The cadence of the version numbers will continue and progress through as they have been, however the preceding “v” will be dropped from the tag.
George
Thanks @georgenalen for that heads up
I'm seeing this warning now (which actually results in an error) when trying to not specify the playbook version. Unsure how long it's been an issue:
$ ansible-galaxy install mindpointgroup.rhel7-stig
[DEPRECATION WARNING]: Ansible will require Python 3.8 or newer on the controller starting with Ansible 2.12. Current version: 3.6.8 (default, Aug 13 2020, 07:46:32) [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)]. This feature will be removed from ansible-core in version 2.12. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
Starting galaxy role install process
downloading role 'RHEL7-STIG', owned by MindPointGroup
[WARNING]: - MindPointGroup.RHEL7-STIG was NOT installed successfully: Unable to compare role versions (0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4, 0.1.5, 0.1.6, 0.1.7, v1.0.0, v1.0.1, 0.2.0, 1.1.0) to determine the most recent version due to incompatible version formats. Please contact the role author to resolve versioning conflicts, or specify an explicit role version to install.
ERROR! - you can use --ignore-errors to skip failed roles and finish processing the list.
This was resolved a few weeks ago