From e21c6138cc0a46bf4cdf30d880f94dd35feaf9ce Mon Sep 17 00:00:00 2001 From: Jeremy Stanley Date: Tue, 16 May 2023 21:32:08 +0000 Subject: [PATCH] Pin ansible-compat<4 until we upgrade ansible-lint There was a regression introduced in ansible-compat v4 which stopped ansible-lint from working. This was fixed in ansible-lint 6.16.0 but we've pinned it for so long now that there are a lot of rule violations to fix or mark for skipping. In the interim, pin back all new versions of ansible-compat until someone has time to fix things or rip out ansible-lint entirely. Change-Id: I62c3ca8731f237ba19868db5d0388d130ea0f214 --- test-requirements.txt | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/test-requirements.txt b/test-requirements.txt index 69c6a3e9..4e3c8489 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -6,8 +6,7 @@ hacking>=4.0.0,<5.0.0 # Apache-2.0 # ansible-lint requires ansible>=2.9 ansible>=5,<6 -# pin until https://github.com/ansible/ansible-lint/issues/2320 is fixed +# pin these two until someone has time to update all our skips to >=6.16 ansible-lint>=6,<6.5 -# avoid for https://github.com/ansible/ansible-compat/issues/258 -ansible-compat!=4.0.1,!=4.0.2 +ansible-compat<4 bashate>=0.2