# Ansible 6.3.0 has been Released! **URL:** \ **Category:** Ansible Project\ **Created:** [August 23, 2022, 8:23pm UTC](https://forum.ansible.com/t/ansible-6-3-0-has-been-released/37028 "2022-08-23T20:23:15Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Christian\_Adams](https://avatars.discourse-cdn.com/v4/letter/c/ba8739/32.png) [@Christian\_Adams](https://forum.ansible.com/u/Christian_Adams)\ **Post date:** [August 23, 2022, 8:23pm UTC](https://forum.ansible.com/t/ansible-6-3-0-has-been-released/37028/1 "2022-08-23T20:23:15Z")
Hi all, We’re happy to announce that the Ansible 6.3.0 package has been released! Ansible 6.3.0 will include ansible-core 2.13.3 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 5.x which included ansible-core 2.12 and there may be backwards incompatibilities in the core playbook language. 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:** [August 24, 2022, 12:28pm UTC](https://forum.ansible.com/t/ansible-6-3-0-has-been-released/37028/2 "2022-08-24T12:28:43Z")
> Hi all, > > We're happy to announce that the Ansible 6.3.0 package has been released! > > Ansible 6.3.0 will include ansible-core 2.13.3 as well as a curated set of > Ansible collections to provide a vast number of modules and plugins. I've updated my RPM building tools at [https://github.com/nkadel/ansiblerepo](https://github.com/nkadel/ansiblerepo) to match. Isn't it time to decouple ansible-core and ansible? The 100 or so third party modules embedded in the tarball called "ansible" do not share the same versions for ansible-core as each other, and ansible-core is still not included as part of the "ansible" tarball. It is installed separately, often as a "pip install" dependency. And as I've mentioned before, the "ansible" tarball does not contain "ansible". It's a bundle of roughly 100 third party modules from the ansible galaxy collection, more properly called "ansible\_collections", and the actual ansible executable script and critical modules are in "ansible-core". This has been going on since the split, which frankly was done backwards. and is as a result very confusing. Frankly, most sites should ignore the ansible tarball. It's too big, and individual components are too erratically maintained, to rely on for high reliability, and the individual ansible galaxy collection modules should be installed only as needed and updated as a checklist, not as a bundle. or as a monolithic package. ansible-core contains the actual executable tools and critical python modules, and frankly should always be installed first. I've previously suggested renaming the "ansible" tarball to an "ansible\_collections" tarball, which would make a lot more sense given that it installs all of its actual content in "ansible\_collections" rooted python directories, and only "ansible-core" installs in "ansible" rooted directories. > This is a major version update from Ansible 5.x which included > ansible-core 2.12 and there may be backwards incompatibilities in the > core playbook language. As I've pointed out repeatedly: the ansible package has \*never\* ansible-core since the very confusing ansible split, back at ansible 2.9, "ansible" now has a listed pip installation requirement of ansible-core which can and should be ignored in most environments They are linked but not directly dependent packages. Please, stop using this confusing language. It would ease deployment for many if they simply installed ansible-core directly, and entirely ignored the bulky and "ansible" tarball, installing only the particular ansible galaxy collection modules they need if and as needed. For most, the "ansible" tarball is no longer an efficient or effective use of their resources.