The Puppet Enterprise Support Lifecycle policy provides guidelines to ensure you are on the version of the product that best serves your organizational needs. Effective May 2017, we made changes to the policies based on customer feedback.
Here are the active versions of Puppet Enterprise with dates regarding their support lifecycle. Mainstream support coincides with the release date; extended support begins on the first calendar day and ends on on the last calendar day of the listed month.
|Active Puppet Enterprise versions
||Start mainstream support
||Start extended support
||End of life
|PE 2018.1 (LTS)
|PE 2019.0 (STS)
In order to support the diverse needs of our customers, we have two different release tracks.
Short term support (STS) releases of Puppet Enterprise are ideal for sites who want the latest capabilities in the Puppet Platform coupled with the best automation workflows in Puppet Enterprise, delivered every six months, for in-place upgrades.
Long term support (LTS) releases of Puppet Enterprise provide the same capabilities of the STS track, at a less frequent cadence for sites who value longevity over new capabilities. Extended support is longer to facilitate migrations.
While LTS releases focus on stabilization and continued support of introduced features, STS releases focus on iterative improvements to forward looking features.
|Release Track →
(Long Term Supported Release)
(Short Term Supported Release)
|Frequency of release
||Every 18 months
||Every 6 months
||18 months from release date
||6 months from release date
||6 months from end of mainstream support
||3 months from end of mainstream support
- Extended migration period
- Fully supported with bug and security fixes, with limited feature iterations
- In-place upgrades to the next LTS release (once available)
- Latest features in every release
- Overlap period with consecutive releases
- In-place upgrades with straightforward compatibility between most versions
During the Mainstream support period, Puppet Enterprise versions receive iterative improvements to released features, security updates and bug fixes. Based on the type of release track chosen (LTS or STS), as explained above, this period lasts for different durations and delivers improvements in line with the core spirit of the release tracks.
This is followed by the Extended support period, during which critical bug fixes and security updates (CVSS scores of 9.0 and higher) will be provided, but no further improvements to features will be delivered. During this time Puppet support team can provide assistance to upgrade to newer LTS or STS versions, as per the Support plans opted by customers.
At the end of the Extended support period, versions enter the End of life (EOL) period where they are no longer eligible for regular security updates and bug fixes. Customers in the process of upgrading to the active Puppet Enterprise versions may contact our technical support team to get assistance with the upgrade process.
Customers on the older inactive versions are strongly encouraged to plan adopting the newer releases to take full benefits of latest features Puppet has to offer. Puppet Enterprise versions 2015.2, 2015.3, 2016.1, 2016.2, 2016.4, 2016.5, 2017.1, 2017.2, and 2017.3 are past the extended support period and have entered the End of Life (EOL) phase as of December 2018. Versions 3.8 and older have been in EOL phase since December 2016. Please contact the technical support team for advice and assistance on moving from an inactive version to a current version of Puppet Enterprise.
Puppet Inc's open-source projects which are upstream of Puppet Enterprise (such as Puppet and Facter) track the maintenance and EOL dates for the PE release streams which depend on them. For example, the PE2018.1 LTS uses Puppet Agent 5.5, so the open source Puppet Agent 5.5 will receive bug fix and security updates until May 2020. For a full list of upstream components in PE releases, see the "Component Versions in Recent PE Releases" page on the docs site.