# Ansible 5.7.0 has been released **URL:** \ **Category:** Ansible Project\ **Created:** [April 26, 2022, 6:33pm UTC](https://forum.ansible.com/t/ansible-5-7-0-has-been-released/36564 "2022-04-26T18:33:57Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![David\_Moreau\_Simard2](https://avatars.discourse-cdn.com/v4/letter/d/c6cbf5/32.png) [@David\_Moreau\_Simard2](https://forum.ansible.com/u/David_Moreau_Simard2)\ **Post date:** [April 26, 2022, 6:33pm UTC](https://forum.ansible.com/t/ansible-5-7-0-has-been-released/36564/1 "2022-04-26T18:33:57Z")
Hi all, We're happy to announce that the Ansible 5.7.0 package has been released ! Ansible 5.7.0 includes ansible-core 2.12 as well as a curated set of Ansible collections to provide a vast number of modules and plugins. This is a major version update from Ansible 4.x which included ansible-core 2.11 and there may be backwards incompatibilities in the core playbook language. Please see the porting guide (linked at the bottom) for details. How to get it ---
**Author:** ![Nico\_Kadel-Garcia](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/nico_kadel-garcia/32/9998_2.png) [@Nico\_Kadel-Garcia](https://forum.ansible.com/u/Nico_Kadel-Garcia)\ **Post date:** [April 28, 2022, 11:24pm UTC](https://forum.ansible.com/t/ansible-5-7-0-has-been-released/36564/2 "2022-04-28T23:24:02Z")
It's having real packagng issues, due to a bug in the python of the fortinet module. See [https://github.com/fortinet-ansible-dev/ansible-galaxy-fortios-collection/issues/180](https://github.com/fortinet-ansible-dev/ansible-galaxy-fortios-collection/issues/180) The bug speaks to the problem of trying to do monolithic bundles of 100 different components. into one tarball of doom and one very large package filled with modules very few ansible users have any use for. It's why I prefer what Fedora packagers have been doing, adding some RPM macros to ansible-core and bundling the ansible galaxy modules as independent RPMs. It makes it much easier to test or update individual components, as needed, rather than burden the ansible server with half a gig of locally installed an unused modules, any one of which may trigger problems with the monolithic tarball as just occurred. I've encountered similar approaches years ago at Akamai, when an architect there insisted that all software be bundled together. It meant that roll-backs of individual components had to roll back \*everything\*. I first peeled the kernel out of the monolithic bundle, and others have since segmented their software more sensibly. Nico Kadel-Garcia