feat!: drop support for ansible-core 2.13 #450
Conversation
|
We could wait for the 20 May 2024 to drop both ansible 2.14 and 2.13 and have a single major release. |
Fine by me. Is there anything to gain from using Python 3.9 features now? (Ansible 2.13 requires support with Python 3.8, 2.14 does not) |
We are still constrained by the python EOL policy that we follow for the hcloud-python library. Maybe we can start using some new feature from ansible-core 2.14, but I think nothing is needed/required right now (maybe some docs improvements). |
jooola
force-pushed
the
drop-ansible-2.13-support
branch
from
41e8236 to
80112df
Compare
|
We will release a new major version anyway, so this is good to go! |
jooola
force-pushed
the
drop-ansible-2.13-support
branch
from
80112df to
e44907d
Compare
🤖 I have created a release *beep* *boop* --- ## [3.0.0](2.5.0...3.0.0) (2024-02-05) ### ⚠ BREAKING CHANGES * drop support for ansible-core 2.13 ([#450](#450)) * always return iso-8601 formatted date time ([#453](#453)) * remove inventory `api_token_env` option ([#454](#454)) ### Features * drop support for ansible-core 2.13 ([#450](#450)) ([96f8009](96f8009)), closes [#400](#400) * **inventory:** allow templating instances hostname ([#455](#455)) ([be404ef](be404ef)) * remove inventory `api_token_env` option ([#454](#454)) ([d0c82ae](d0c82ae)) ### Bug Fixes * allow renaming networks ([#449](#449)) ([742cfe6](742cfe6)) * always return iso-8601 formatted date time ([#453](#453)) ([55d2616](55d2616)) * load balancer invalid cookie lifetime value returned ([#452](#452)) ([86b7662](86b7662)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
SUMMARY
ansible-core 2.13 is EOL since 6 November 2023.
Fixes #400
https://docs.ansible.com/ansible/latest/reference_appendices/release_and_maintenance.html#ansible-core-support-matrix