Allow version lock to specific Ansible Creator Execution Environment about ansible-lint-action HOT 1 CLOSED

While we will not allow override of any tools versions, we will ensure that this action versioning will be relevant to linter and ansible version by using creator-ee tags.

Basically fixing this needs some changes to how we publish creator-ee images, so we can expose that information. Sadly there is longer chain of this that need to happen until we can fix this but do not lose hope, we are fully aware of this issue and we want to fix it.

As we can have only one version number exposed, I wonder how should we combine the two versions, linter and core into one version number, that is still relevant and easy to understand. We also need to keep it compatible with dependabot version bumping for actions. Any suggestions?

Regarding python version, we will always try to use latest stable version of python supported by ansible-core, so there is no need to mention it inside action version, but we can include information in container metadata, to ease debugging.

from ansible-lint-action.