The initial PR for updating to Python 3.12 was missing a metadata update
for publishing supported version ranges to package distributions.
While updating this I noticed that other actions were explicitly testing against
Python 3.9 due to a dependency on an old composite action hard-coded to
3.9 from way back when the Transform product only supported that Python version.
I've taken the liberty of updating all of these actions to use matrix strategies that
test either the complete set of supported Python versions (unit tests) or the min and
max supported Python versions (development-focused actions).
The initial PR for updating to Python 3.12 was missing a metadata update for publishing supported version ranges to package distributions.
While updating this I noticed that other actions were explicitly testing against Python 3.9 due to a dependency on an old composite action hard-coded to 3.9 from way back when the Transform product only supported that Python version. I've taken the liberty of updating all of these actions to use matrix strategies that test either the complete set of supported Python versions (unit tests) or the min and max supported Python versions (development-focused actions).