Puppet releases and lifecycle
Open source Puppet has two release tracks:
- Developmental releases: Puppet versions not associated with any PE version release new minor (or “y”) version about once a month. Developmental releases typically do not get patch (or “z”) releases. Each minor release in this stream supersedes the previous minor release. Documentation for the current developmental release is available at
puppet.com/docs/puppet/latest. See the release notes for updates to this release stream.
- Long-term releases: Puppet versions associated with Puppet Enterprise get patch (or “z”) releases a few times a year. Each release contains fixes and features from several developmental releases. Versioned documentation for long-term releases is available at
puppet.com/docs/puppet/<X.Y>(for example, puppet.com/docs/puppet/6.4).
Important: To ensure that you have the most recent features, fixes, and security patches, update your Puppet version whenever there is a new version in your release track.
This version of Puppet is a long-term release. The table below lists the associated Puppet, Puppet Server, PuppetDB, and Puppet Enterprise versions, with links to their respective documentation. Open source releases that are associated with PE versions have projected End of Life (EOL) dates.
For a complete list of the maintained versions of Puppet, PuppetDB, and Puppet Server, see the most recent Puppet versions page.
|Puppet version||Puppet Server version||PuppetDB version||Associated PE version||EOL date|
For information about Puppet’s operating system support, see the platform support lifecycle page.
We distribute open source Puppet as two core packages and one optional package.
puppet-agent: This package contains Puppet’s main code and all of the dependencies needed to run it, including Facter, Hiera, and bundled versions of Ruby and OpenSSL. After it’s installed, you have everything you need to run the Puppet agent service and the puppet apply command.
puppetserver: Puppet Server is a JVM-based application that, among other things, runs instances of the Puppet master application and serves catalogs to nodes running the agent service. It has its own version number and might be compatible with more than one Puppet version. This package depends on puppet-agent. After it’s installed, Puppet Server can serve catalogs to nodes running the agent service.
puppetdb: PuppetDB (optional) collects data generated by Puppet. It enables additional features such as exported resources, advanced queries, and reports about your infrastructure.
Deprecation Note: As of Puppet agent 5.5.4, MCollective is deprecated and will be removed in a future version of Puppet agent. If you use Puppet Enterprise, consider moving from MCollective to Puppet orchestrator. If you use open source Puppet, migrate MCollective agents and filters using tools such as Bolt and PuppetDB’s Puppet Query Language.
puppet-agent component version numbers
puppet-agent package contains several components. This table shows the components shipped in this release track, and contains links to available component release notes.
Note: Hiera 5 is a backward-compatible evolution of Hiera, which is built into Puppet. To provide some backward-compatible features, it uses the classic Hiera 3 codebase. This means Hiera is still shown as version 3.x in the table above, even though this Puppet version uses Hiera 5.