Puppet End of Life (EOL) Dates and End of Support (EOS) Dates

Latest Release: 8.18.0

Puppet end of life (EOL) and end of support (EOS) dates: 5 Puppet versions have reached EOL, including Puppet 7 (EOL date: Apr 30, 2025) — no longer receiving security updates or patches. Puppet 8.18.0 is the current supported release. Also see Apache Subversion EOSL information for related end-of-life information.

Puppet end of life dates timeline — release schedule chart of the 6 most recent Puppet versions, mapping security support windows against their EOL dates
Puppet end of life dates and end of support (EOS) dates shown as a release schedule — support windows for the 6 most recent Puppet releases. Each bar runs from the release date to the end of security support, with the dashed line marking today. Exact Puppet EOL, EOS and EOSL dates for every version are listed in the tables below.

Currently Supported Puppet Releases - Active EOS/EOSL Support (1)

Release Released Supported Latest
8 (3 years and 7 months ago) Active 8.18.0 (7 months ago)

Puppet End of Life (EOL) Releases - No Longer Supported (5)

Release Released Supported Latest
7 (6 years ago) (1 year and 6 months ago) 7.35.0 (1 year and 8 months ago)
6 (8 years and 2 months ago) (3 years and 9 months ago) 6.29.0 (3 years and 9 months ago)
5 (9 years and 4 months ago) (5 years and 10 months ago) 5.5.22 (6 years and 1 month ago)
4 (11 years and 7 months ago) (8 years and 1 month ago) 4.10.13 (7 years and 11 months ago)
3 (14 years and 1 month ago) (9 years and 10 months ago) 3.8.7 (10 years and 6 months ago)

Knowing when Puppet end of life arrives for your version tells you how long Puppet Enterprise keeps receiving security fixes. Perforce, which now maintains the product, publishes the dates, and customers who track them avoid running unsupported systems.

Puppet Enterprise EOL and Lifecycle Policy

The Puppet Enterprise lifecycle and its lifecycle policy decide which releases get technical support and maintenance releases, and when the end of support date falls. Past that date no patches arrive for Puppet Enterprise, so the only safe move is an upgrade to a release that Puppet Enterprise still supports. Longer coverage exists only as extended support, sold as a premium offering to teams with strict compliance duties.

Latest and Latest-1 Support Model

Starting with PE 2026.0, planned for August 2026, a simpler support model replaces LTS. The Latest series, the newest major version, gets full active support for 12 months: new features, security updates, defect fixes and technical support. When the next major version ships, the old one becomes Latest-1 and gets limited active support for another 12 months, covering security updates, defect fixes and minor changes only. Each release track delivers minor releases quarterly, so this lifecycle model gives each release series about two years of life, and its dates stay projected until confirmed. After that the series reaches end of support.

Legacy Model: Long-Term Support (LTS)

The legacy model gave each LTS version up to two years of support, then a six-month overlap support period to ease migration. PE 2023.8.z is the final LTS supported release: maintenance ends August 27, 2026, the overlap ends February 27, 2027, and it then reaches end of maintenance and support (EOMS). No later LTS release will exist.

Puppet End of Life Schedule by Version

This table shows the GA date and support status of each series Puppet publishes.

VersionTrackGA dateSupport status
PE 2025.yLatestDecember 12, 2024Full support until PE 2026.0, then limited support until August 2027
PE 2023.8.zLTS (final)August 27, 2024Maintenance until August 27, 2026, overlap until February 27, 2027

These are the currently supported versions, and the dates above are their end dates. Each subscription license covers every nodes you manage under the same dates, whatever the operating system: the primary server runs on Linux, while agents also cover Windows and other platforms. Read the release notes before each deployment to see when your series loses support.

Unsupported Versions and Support Risks

Unsupported versions receive no fixes, so every new vulnerability stays open in your infrastructure, and auditors reviewing compliance will flag it. Any Puppet Enterprise release older than the Latest-1 series is already past support, and once a series is end-of-life you should treat it as a risk and replace it with the Latest release. DevOps teams should watch each announcement from Perforce.

Puppet Core EOL and Open Source Puppet

Puppet Core is the proprietary build Perforce develops for versions 8 and 9, while open source Puppet 7 ended in April 2025. Core follows the last Enterprise release on its track, as this table shows.

Major versionProjected end dateBasis
Puppet Core 9.xFebruary 2029Follows EOMS of PE 2026.y
Puppet Core 8.xFebruary 2028Follows EOMS of PE 2025.y
Puppet Core 7.xApril 2025Superseded by Puppet Core 8.12.0

Releases unrelated to Enterprise follow an update track with a new minor version about monthly. Because Puppet drives configuration management and automation and bundles Ruby, an unsupported series leaves all of that unpatched, so run puppet --version to learn which series you use.

Component Support for Facter and Hiera

Bundled pieces such as Facter and Hiera share the lifecycle of the release that ships them, so component support ends with it. The platform page lists component versions and compatibility between agent, Puppet Server and PuppetDB.

Puppet Platform Lifecycle: Puppet Agent and Puppet Server Packages

The platform ships as packages. The agent package carries the main code with Facter and Hiera, and Puppet Server, a Linux-only service, delivers catalogs to the agent on your servers. Agent and server packages are supported only as part of the Puppet Enterprise or Puppet Core release that ships them, so they reach end of life when that release does. The agent has its own version, so confirm it against the primary server before you upgrade.

Comply and Continuous Delivery EOL Notices

Perforce ended Continuous Delivery 4.x and Comply 2.x on February 5, 2026. Comply 2.x was the old Security Compliance Management product, and its replacement is version 3.x.

Support Lifecycle Planning: Security Updates, Defect Fixes and Upgrade Timing

Use this checklist to avoid surprises:

  • List every Puppet version in production and map it to the dates above.
  • Run the Latest Puppet Enterprise release where you can, and keep Latest-1 only as a short stop.
  • Plan to migrate from PE 2023.8.z before February 27, 2027.
  • Test each migration in staging, then roll it out in batches.

Puppet Enterprise 2025.y stays on the Latest track until PE 2026.0 arrives, then moves to Latest-1 and is projected to run out of support in August 2027, while Puppet Enterprise 2023.8.z has the nearer deadline. Because security fixes stop with support, keep your compliance evidence and infrastructure on a supported build.

EOL dates of related software products