Robin Candau pushed to branch main at Arch Linux / Packaging / Packages / ansible
Commits: 225e6799 by Robin Candau at 2024-08-22T15:36:57+02:00 Improve wording in README - - - - - 1 changed file: - README.md Changes: ===================================== README.md ===================================== @@ -6,7 +6,7 @@ The `ansible` upstream source (which provides community modules/collections for However, they do not share a similar/synced version scheme nor have any mechanism that would clearly indicate this when packaging it; apart from a note in their [changelogs](https://forum.ansible.com/t/release-announcement-ansible-community-package-10-3-0/7821) (e.g. from the changelog linked: "Ansible 10.3.0 depends on ansible-core 2.17.3 [...]"). In other words, `ansible` new releases *silently* depend on the latest `ansible-core` version available at the time. -To put it simply, `ansible` should always be built against an up to date version of `ansible-core`. Building new `ansible` releases against outdated versions of `ansible-core` will inevitably create incompatibility issues for some community modules. +To put it simply, `ansible` new releases should always be built against an up to date version of `ansible-core`. Building new `ansible` releases against outdated versions of `ansible-core` would inevitably create incompatibility issues for some community modules. Fortunately, upstream usually syncs the releases of new `ansible` and `ansible-core` versions. They are usually released a few hours apart (with `ansible-core` always being released first). View it on GitLab: https://gitlab.archlinux.org/archlinux/packaging/packages/ansible/-/commit/225e6799facd84bbe4b8a8d7df0755bfadbf42ad -- View it on GitLab: https://gitlab.archlinux.org/archlinux/packaging/packages/ansible/-/commit/225e6799facd84bbe4b8a8d7df0755bfadbf42ad You're receiving this email because of your account on gitlab.archlinux.org.
