Ansible-Core March 2026 Releases: v2.16.18, v2.18.15, v2.19.8, and v2.20.4

Introduction

March 2026 brought a wave of ansible-core maintenance releases across all four supported branches. Whether you're running the latest 2.20 series or maintaining older playbooks on 2.16, there's something relevant for your environment.

This article summarizes all four releases, highlights the most important changes, and provides upgrade guidance.

See also: Ansible Core 2.21.0b3: What's New in the Latest Beta (Preview Guide)

ansible-core 2.20.4 (March 23, 2026)

The latest stable release includes several notable fixes:

Key Bugfixes

• PowerShell shell commands fix — Fixed command execution when using connection plugins that don't support stdin/pipeline input (#86397) • rpm_key module update — Now uses the librpm library API instead of the gpg utility, adding support for PGP version 6 keys (#86157) • ansible-connection pickling fix — Prevents unpickling failures in module contexts by converting AnsibleTaggedObjects to plain types in JsonRpcServer • YAML loading fix — Resolves traceback when parsing YAML strings using the pure Python PyYAML implementation • Config lookup — Now uses pre-existing constants for templating when needed

Minor Changes

• ansible-test — Added container/remote aliases for more flexible managed test environments • ansible-test — Added support for using Ansible Core CI from GitHub Actions

How to Upgrade

pip install ansible-core==2.20.4 --upgrade
ansible --version

ansible-core 2.19.8 (March 2026)

A maintenance release for the 2.19 branch, focusing on stability and compatibility improvements. This branch receives regular bugfix updates and is recommended for production environments not yet ready for 2.20.

pip install ansible-core==2.19.8 --upgrade

See also: Ansible 13 Upgrade Guide: Breaking Changes, Removals, and Migration Steps

ansible-core 2.18.15 (March 2026)

The 2.18 branch continues to receive security and critical bugfix patches. If you're on this branch, upgrading to the latest patch is recommended to stay current with fixes.

pip install ansible-core==2.18.15 --upgrade

ansible-core 2.16.18 (March 2026)

The 2.16 branch is in extended maintenance. This release contains targeted bugfixes. Note that 2.16 is approaching end-of-life — plan your migration to a newer branch.

pip install ansible-core==2.16.18 --upgrade

See also: Ansible 14.0.0a3 Pre-Release: What's New in Ansible 14 (Preview)

Which Version Should You Use?

| Branch | Status | Recommendation | |--------|--------|----------------| | 2.20.x | Latest stable | Recommended for new projects and environments | | 2.19.x | Active maintenance | Good for production, stable and well-tested | | 2.18.x | Security fixes only | Upgrade to 2.19 or 2.20 when possible | | 2.16.x | Extended maintenance | Plan migration — approaching EOL |

Checking Your Current Version

# Check installed version
ansible --version
# Check available updates
pip index versions ansible-core

Best Practices for Upgrading

Test in staging first — Run your playbook test suite against the new version Check the porting guide — Review breaking changes between major versions Update gradually — Jump one major version at a time (2.16 → 2.18 → 2.19 → 2.20) Pin your version — Use ansible-core==2.20.4 in requirements files, not ansible-core>=2.20

Conclusion

Keeping ansible-core updated ensures you benefit from the latest bugfixes, security patches, and compatibility improvements. The March 2026 releases are maintenance-focused, making them safe to adopt quickly. Check the full changelog on GitHub for complete details.

Related Articles

• Ansible Bullhorn #223: ansible-core Releases, New Collections & AI Collaboration