fix(deps): exclude ansible-core 2.17.x (CVE-2026-11332) (#588)

ansible-core 2.17 is EOL and will never receive the fix for
CVE-2026-11332 (argument injection in ansible-galaxy role install,
CVSS 7.8). Exclude the entire 2.17.x range so the resolver picks
2.16.19 (patched) for Python 3.10 or 2.18+ for Python 3.11+.

fix: drop milestone from Python 3.12 matrix (#576)

fix: bump cryptography and cairosvg constraint floors for CVE remedia…

…tion (#575)

Raise cryptography constraint from >=43 to >=49.0.0 to address
CVE-2026-39892 (buffer overflow), CVE-2026-26007 (subgroup attack),
and GHSA-537c-gmf6-5ccf (vulnerable OpenSSL in wheels).
Add cairosvg>=2.9.0 constraint to prevent resolution to versions
vulnerable to CVE-2026-31899 (exponential DoS via recursive <use>).

chore(deps): update all dependencies to df4cb1c (#560)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Sudhir Verma <9924513+sudhirverma@users.noreply.github.com>

chore: update test deps (#537)

fix: handle tox 4.47+ conflicting version factors in env names (#535)

* fix: set ignore_base_python_conflict to resolve tox 4.47+ version factor conflicts

* fix: explicitly set base_python to prevent tox 4.47+ version conflicts

tox 4.47.1 treats bare version numbers like 2.16 as Python versions,
causing environment names like sanity-py3.10-2.16 to fail with
"conflicting factors py3.10, 2.16" error.

The previous fix (ignore_base_python_conflict=True) suppressed the error
but caused tox to fall back to the default Python (3.10), which fails
when ansible-core requires a newer Python version.

This fix explicitly sets base_python for each environment based on the
Python version factor (e.g., py3.11 → base_python=py3.11), ensuring tox
uses the correct Python interpreter.

Made-with: Cursor

* fix: use expected_factors constant to satisfy linter

Made-with: Cursor

* fix: shorten lines to satisfy 100 char limit

Made-with: Cursor

* fix: exclude empty base_python from loader to avoid config failures

When base_python is empty (e.g., for the galaxy environment which
doesn't follow the {test_type}-py{version}-{ansible} naming pattern),
including it in the MemoryLoader causes tox to fail finding a Python
interpreter. Only include base_python when we have a specific version.

Made-with: Cursor

* test: add coverage for galaxy env without base_python

Add test case for environments like 'galaxy' that don't follow the
standard {test_type}-py{version}-{ansible} naming pattern. This
ensures base_python is excluded from the loader when not applicable.

Made-with: Cursor

* chore: trigger CI

Made-with: Cursor

* ensure we use correct tox versions

---------

Co-authored-by: anushka-shukla-03 <anshukla@redhat.com>
Co-authored-by: Sorin Sbarnea <sorin.sbarnea@gmail.com>

chore(deps): update all dependencies (#532)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

chore: remove sugar argument on pytest (#530)

As pytest-ansible remove dependency on pytest-sugar, we stop using
it.

Enable 2.16 still supported by AAP 2.5 (#517)

* Enable 2.16 still supported by AAP 2.5

* tes

* Update size

* Update workflow to ignore tests

* Only ignore for 2.16

chore: Add check for platform version (#513)