Only test latest bugfix releases in main matrix; move initial minor r…

…eleases to special cases.

.github/workflows/ansible-test.yml

@@ -77,11 +77,9 @@ jobs:
           - fedora40
         sops_version:
           - 3.5.0
-          - 3.6.0
+          - 3.6.1
           - 3.7.3
-          - 3.8.0
           - 3.8.1
-          - 3.9.0
           - 3.9.1
         python_version:
           - ''
@@ -133,6 +131,18 @@ jobs:
             docker_container: ubuntu2404
             sops_version: 3.9.0
           # devel
+          - ansible: devel
+            docker_container: ubuntu2204
+            sops_version: 3.6.0
+          - ansible: devel
+            docker_container: ubuntu2204
+            sops_version: 3.7.0
+          - ansible: devel
+            docker_container: ubuntu2404
+            sops_version: 3.8.0
+          - ansible: devel
+            docker_container: fedora40
+            sops_version: 3.9.0
           - ansible: devel
             docker_container: quay.io/ansible-community/test-image:archlinux
             python_version: '3.12'

README.md

@@ -19,11 +19,9 @@ Please note that this collection does **not** support Windows targets.
 
 The following table shows which versions of SOPS were tested with which versions of the collection. Older (or newer) versions of SOPS can still work fine, it just means that we did not test them. In some cases, it could be that a minimal required version of SOPS is explicitly documented for a specific feature. This is the case from community.sops 1.8.0 on; from that version on the collection automatically detects the SOPS version to determine whether a feature is supported or not.
 
-|`community.sops` version|SOPS version|
+|`community.sops` version|SOPS versions|
 |---|---|
-|0.1.0|`3.5.0+`|
-|1.0.6|`3.5.0+`|
-|`main` branch|`3.5.0`, `3.6.0`, `3.7.3`, `3.8.0`, `3.8.1`, `3.9.0`, `3.9.1`|
+|`main` branch|`3.5.0`, `3.6.0`, `3.6.1`, `3.7.3`, `3.8.0`, `3.8.1`, `3.9.0`, `3.9.1`|
 
 ## Code of Conduct