collection: `ansible-lint` does not like `latest` in `requirements.yml`

[berndfinger]

I tested using ansible-lint versions 24.9.0 and 24.9.2.

The version of requirements.yml producing this error contains:

  - name: community.general
    version: latest
    type: galaxy

The error message when running ansible-lint on the collection is:

ERROR! Unexpected Exception, this is probably a bug: Non integer values in LooseVersion ('latest')

The version of requirements.yml not producing this error contains:

  - name: community.general
    version: '>=9.5.0'
    type: galaxy

Note: The collection community.general version 9.5.0 is currently the latest one and has been published on Ansible Galaxy 23 days ago, see https://galaxy.ansible.com/ui/repo/published/community/general/.

[marcelmamula]

@berndfinger This looks like very strange issue with state data type.

[kksat]

Looks like there is a workaround

https://docs.ansible.com/ansible/5/user_guide/collections_using.html#installing-an-older-version-of-a-collection

Ansible will always install the most recent version that meets the range identifiers you specify. You can use the following range identifiers:

*: The most recent version. This is the default.

Solution would be either use '*' or no version at all.

  - name: community.general
    version: '*'
    type: galaxy

[berndfinger]

I think it's better to specify a minimum version.