amazon.aws VS news-for-maintainers

amazon.aws 6.4.0 has been released with a new module named amazon.aws.ec2_key_info, some documentation improvements, new features and bugfixes (see changelog for details).

amazon.aws 5.5.1 has been released with several bugfixes (see changelog for details).

amazon.aws 5.5.0 has been released with a number of bugfixes, new features and new modules. This is the last planned minor release prior to the release of version 6.0.0 (see changelog for details).

amazon.aws 5.4.0 has been released with bugfixes for the ec2_metadata_facts, ec2_vol, rds_instance and route53_info modules, as well as feature enhancements for the ec2_spot_instance and route53_health_check modules - see changelog for details.

Hi folks! I'm one of the docs writers for community Ansible (aka docs.ansible.com, not access.redhat.com). It sounds like you've found a place to log your docs problems already but I did open an issue on the amazon.aws collection directly to handle the examples that aren't quoted for `filters` at https://github.com/ansible-collections/amazon.aws/issues/1331

The amazon.aws collection version 5.0.0 has been released. See the changelog for details on new modules and features.

amazon.aws 4.0.0 has been released with some new features, bugfixes, breaking changes and deprecated features. The amazon.aws collection has also dropped support for botocore<1.20.0 and boto3<1.17.0 (see changelog for details).

amazon.aws 2.2.0 has been released with bug-fixes (see changelog for details).

amazon.aws 3.1.1 has been released with some new features, bugfixes and a deprecation (see changelog for details). 3.1.0 failed to publish on Galaxy, hence, we had to bump the release version.

The AWS community has begun planning for the 4.0.0 releases of amazon.aws and community.aws. Please see the linked issues for more details or to get involved.

If you are using GHA to run tests on collections, you might have noticed strange failures when using ansible-test's --docker option when using ubuntu-latest. Read more about this and how to fix this in this issue.

In ansible/ansible, the stable-2.13 branch has been created (more infos), and the version of the devel branch has been bumped to 2.14.0.dev0 (more infos).

If you want to discuss this, we welcome feedback in ansible-collections/news-for-maintainers/discussions/4.

In accordance with the Community decision, we have created the news-for-maintainers repository for announcements of changes impacting collection maintainers (see the examples) instead of Issue 45 that has just been closed. To keep yourself well-informed and, therefore, things in your collection working, please subscribe to the repository by using the Watch button in the upper right corner on the repository's home page. If you do not want to get notifications about related discussions, please subscribe only to Issues. Please read the brief guidelines on how the repository should be used. Please avoid unnecessary discussions in issues, use the Discussions feature. Every comment posted will notify a lot of folks!