← ← Back to all products
Puppet
Active
DevOps & CI/CDLatest Version: 8.18.0Latest Release: Apr 10, 2026
Puppet is an infrastructure automation tool for managing configuration and state of servers.
Support summary
Puppet currently has supported cycles. Track the next EOL date and validate upgrades before your change window.
What do EOL and support statuses mean?Next EOL
No announced EOL date is currently listed.
Supported cycles
1
0 lts
Versions
6
Latest Version
8.18.0
Active Support
1
EOL
5
Lifecycle Timeline
Today ↓
8
8
7
7
6
6
5
5
4
4
3
3
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 8 | Apr 21, 2023 | Yes | No | 8.18.0 | No | Active |
| 7 | Nov 13, 2020 | No | Apr 30, 2025 | 7.35.0 | No | EOL |
| 6 | Sep 18, 2018 | No | Feb 1, 2023 | 6.29.0 | No | EOL |
| 5 | Jun 27, 2017 | No | Jan 1, 2021 | 5.5.22 | No | EOL |
| 4 | Apr 8, 2015 | No | Oct 1, 2018 | 4.10.13 | No | EOL |
| 3 | Sep 28, 2012 | No | Jan 1, 2017 | 3.8.7 | No | EOL |
Data sources
Sources
Frequently Asked Questions
Which versions of Puppet have reached end of life?
The following Puppet versions have reached end of life and no longer receive security updates: 7, 6, 5, 4, 3. It is recommended to upgrade to a supported version.
Is it safe to continue using Puppet 7?
Puppet 7 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Puppet?
The latest version of Puppet is 8.18.0, released in the 8 release cycle.
How many versions of Puppet are currently supported?
Puppet currently has 1 actively supported version(s): 8.
When does Puppet 8 reach end of life?
Puppet 8 does not have a specific end-of-life date announced yet.
What should I do when Puppet reaches end of life?
When a Puppet version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.