From d0ef7a823150ea84e0fbb8d54711dfbe8fb9e477 Mon Sep 17 00:00:00 2001 From: Carlos Goncalves Date: Fri, 10 Jan 2020 14:35:52 +0100 Subject: [PATCH] Cap hacking version to <2 Hacking received a major update to version 2.0.0 that added new checks that fail on stable branches. Instead of addressing those new check errors on stable branches, it is better to cap hacking to <2. This way we'll not see lint errors again should new checks be added in the future. Support for hacking 2.0.0 in master branch is being worked in https://review.opendev.org/#/c/699302/ Change-Id: I4706972095d42815a3f3cec0bc5aa82a34922bf3 (cherry picked from commit 85f7abbbaf958458ee12415b0de0e938c20fb121) --- test-requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test-requirements.txt b/test-requirements.txt index 8e0b2e39c6..14be4f6dbc 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -1,7 +1,7 @@ # The order of packages is significant, because pip processes them in the order # of appearance. Changing the order has an impact on the overall integration # process, which may cause wedges in the gate later. -hacking!=0.13.0,<0.14,>=0.12.0 # Apache-2.0 +hacking!=0.13.0,<0.14,>=0.12.0,<2 # Apache-2.0 requests-mock>=1.2.0 # Apache-2.0 coverage!=4.4,>=4.0 # Apache-2.0 flake8-import-order==0.12 # LGPLv3