We are pumped to announce the release of: mistral-tempest-plugin 2.6.0 This release is part of the epoxy release series. The source is available from: https://opendev.org/openstack/mistral-tempest-plugin Download the package from: https://tarballs.openstack.org/mistral-tempest-plugin/ Please report issues through: https://bugs.launchpad.net/mistral/+bugs For more details, please see below. Changes in mistral-tempest-plugin 2.5.0..2.6.0 ---------------------------------------------- a707405 Skip testing v2/services endpoint fa04f94 Skip installation to speed up pep8 6201194 Bump hacking ada1ee3 Update gate jobs as per the 2025.1 cycle testing runtime 242633c perfect invalid cron pattern out of range test scenarios 44c6fb0 add delete nonexist workbook testcase 744246e modify get task details use the get_object method b6c8f24 Cleanup py27 support 991ee74 Revert "Skip test_cinder_action test" Diffstat (except docs and test files) ------------------------------------- .zuul.yaml | 11 +++++++++++ .../scenario/engine/actions/v2/test_openstack_actions.py | 1 - requirements.txt | 6 +++--- setup.py | 8 -------- test-requirements.txt | 6 +----- tox.ini | 1 + 10 files changed, 39 insertions(+), 23 deletions(-) Requirements updates -------------------- diff --git a/requirements.txt b/requirements.txt index 3c3206f..fcf948a 100644 --- a/requirements.txt +++ b/requirements.txt @@ -1,3 +1,3 @@ -# 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. +# Requirements lower bounds listed here are our best effort to keep them up to +# date but we do not test them so no guarantee of having them all correct. If +# you find any incorrect lower bounds, let us know or propose a fix. diff --git a/test-requirements.txt b/test-requirements.txt index 7ef9f3d..3d2e1c5 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -1,5 +1 @@ -# 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>=3.0.1,<3.1.0 # Apache-2.0 +hacking>=6.1.0,<6.2.0 # Apache-2.0