[#187593014] Use Ansible 2.17/2.18 for testing

Rheinwerk · Jun 5, 2024 · 8c1a13b · 8c1a13b
1 parent 92947d5
commit 8c1a13b
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 6 deletions.
diff --git a/action.yml b/action.yml
@@ -6,10 +6,10 @@ author: Michael Schmitz
 inputs:
   ansible_current_version:
     description: Ansible version to use for 'ansible_current' scenario
-    default: '==2.13.*'
+    default: '==2.17.*'
   ansible_next_version:
     description: Ansible version to use for 'ansible_next' scenario
-    default: '==2.16.*'
+    default: '==2.18.*'
   ansible_version:
     description: Ansible version to use, leave empty for newest
     default: ''
@@ -140,4 +140,4 @@ runs:
         MOLECULE_DISTRO: "${{ inputs.distro }}"
         MOLECULE_SCENARIO_NAME: "${{ inputs.molecule_scenario }}"
         PY_COLORS: '1'
-        TEST_TYPE: "${{ inputs.test_type }}"
+        TEST_TYPE: "${{ inputs.test_type }}"
diff --git a/requirements/collections_ansible_current.yml b/requirements/collections_ansible_current.yml
@@ -4,9 +4,6 @@ collections:
   - name: ansible.netcommon
   - name: ansible.posix
   - name: ansible.utils
-  # The last known version compatible with ansible-core<2.14 is `v2.12.0`
-  - name: ansible.utils
-    version: 2.12.0
   - name: community.aws
   - name: community.crypto
   - name: community.docker