From 5ea986434fa8de32b2af116a4e5e0a7c5b3215d0 Mon Sep 17 00:00:00 2001 From: Ian Wienand Date: Wed, 1 Feb 2023 13:43:34 +1100 Subject: [PATCH] linters-requirements : update Ansible to 2.12, ansible-lint <6.12.0 The recent release of ansible-compat, which is pulled in by ansible-lint, has dropped support for Ansible < 2.12. This was pinned by I233fae8c9036d295968a97ee80e07fde8846c633 and it's not really clear to me why the upper-bound was added then. I think we can just uncap this? It doesn't match Zuul at the moment anyway which is Ansible 6 (2.13). Also, since the first revision of this change, ansible-lint 6.12.0 came out. We are not ready for it, so we need to squash a cap for it into this change to unbreak the gate. [1] https://github.com/ansible/ansible-compat/releases/tag/v3.0.0 Change-Id: I901769a133ab3cf68fe314940cd359e54dfd5353 --- linters-requirements.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/linters-requirements.txt b/linters-requirements.txt index bfff238c2..2c0ef4b22 100644 --- a/linters-requirements.txt +++ b/linters-requirements.txt @@ -1,8 +1,8 @@ # linters have different requirements than test ones, some would # conflict, like ansible version required by ansible-lint. -ansible>=2.9,<2.11 # required by ansible-lint +ansible>=2.12.0 # required by ansible-lint flake8 yamllint>=1.23.0 # 6.5.0 : https://github.com/ansible/ansible-lint/issues/2330 # 6.5.1 : https://github.com/ansible/ansible-lint/issues/2320 -ansible-lint>6.8.0 +ansible-lint>6.8.0,<6.12.0