Cap hacking to avoid gate failure
instead of fixing all new violaions appearing with new hacking releases, just cap hacking to latest that was applicable when stable release was cut. Change-Id: Ib9019fb15aee13749ba68c8d8d2ae77b4cb281e0
This commit is contained in:
parent
38ccb4fcec
commit
bd77b6ef76
|
@ -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>=1.0.0 # Apache-2.0
|
||||
hacking>=1.0.0,<1.1.0 # Apache-2.0
|
||||
coverage!=4.4,>=4.0 # Apache-2.0
|
||||
doc8>=0.6.0 # Apache-2.0
|
||||
fixtures>=3.0.0 # Apache-2.0/BSD
|
||||
|
|
Loading…
Reference in New Issue