LoginSign Up
← Back to all sparks
A

Ansible

INFRA · APIS
Velocity5.0

Agentless IT automation and configuration management engine

www.ansible.com ↗

Ansible core cuts four maintenance branches in lockstep — and publishes checksums, not changelogs.

configuration managementmaintenance branchesrelease candidatesbackportsopen source
◆Current state
Ansible core is running four supported branches in parallel — 2.18 through 2.21 — and on August 3 all four cut release candidates inside a twelve-minute window. The feed itself carries no changelog text: each entry is a wheel name, a tarball name and two SHA-256 sums, with the actual notes behind a link. What shipped is therefore not observable from this feed, only that it shipped everywhere at once.
◆Where it's heading
This is maintenance cadence, not feature work. The June pattern repeats the August one: 2.18.18 and 2.19.11 went final two minutes apart, and now four branches cut candidates together. Coordinated same-day backports across every supported branch is the shape of a single fix being carried everywhere rather than independent branch roadmaps.
◆Prediction
The four August 3 release candidates should promote to final releases within a few weeks, following the June cadence. What is driving the synchronized backport cannot be determined from these entries — the feed publishes artifacts and hashes only.

◆Recent moves

  1. 2d ago

    ansible-core 2.21.3 release candidate

    A release candidate on the newest supported branch, cut within minutes of candidates on the other three. The entry carries artifact names and hashes only, so no user-visible change can be read from it.

    View source ↗
  2. 2d ago

    ansible-core 2.20.8 release candidate

    The 2.20 branch's slice of the same August 3 backport sweep. Nothing in the entry distinguishes it from its three siblings beyond the version and the checksums.

    View source ↗
  3. 2d ago

    ansible-core 2.19.12 release candidate

    Third of the four simultaneous candidates, keeping the 2.19 branch level with the rest. Artifact metadata only; the substance lives in the linked changelog.

    View source ↗
  4. 2d ago

    ansible-core 2.18.19 release candidate

    The oldest supported branch still receives the same backport on the same day, which is the clearest signal here about how far coverage extends. No feature content is present in the entry.

    View source ↗
  5. 1mo ago

    ansible-core 2.21.2 release candidate

    The previous 2.21 candidate, a month ahead of the August sweep and unaccompanied by sibling branches. Contents are not visible in the feed.

    View source ↗
  6. 1mo ago

    ansible-core 2.18.18 final release

    A final release on the oldest supported branch, published within two minutes of 2.19.11 — the June instance of the same paired-branch pattern seen again in August. Checksums only, no notes.

    View source ↗