← ← Back to all products
Chef Workstation
Active
DevOps & CI/CD Latest Version: 25.12.1102 Latest Release: Dec 12, 2025
Chef Workstation provides tools for authoring and testing Chef infrastructure automation code.
Versions
6
Latest Version
25.12.1102
Active Support
2
EOL
4
Lifecycle Timeline
Today ↓
25
25
24
24
23
23
22
22
21
21
20
20
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 25 | Feb 3, 2025 | Yes | No | 25.12.1102 | No | Active |
| 24 | Feb 7, 2024 | Yes | No | 24.12.1073 | No | Active |
| 23 | Feb 9, 2023 | Dec 31, 2024 | Dec 31, 2024 | 23.12.1055 | No | EOL |
| 22 | Jan 6, 2022 | Dec 31, 2024 | Dec 31, 2024 | 22.12.1024 | No | EOL |
| 21 | Jan 5, 2021 | Dec 31, 2024 | Dec 31, 2024 | 21.12.720 | No | EOL |
| 20 | Jun 2, 2020 | Dec 31, 2024 | Dec 31, 2024 | 20.12.205 | No | EOL |
Frequently Asked Questions
Which versions of Chef Workstation have reached end of life?
The following Chef Workstation versions have reached end of life and no longer receive security updates: 23, 22, 21, 20. It is recommended to upgrade to a supported version.
Is it safe to continue using Chef Workstation 23?
Chef Workstation 23 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 Chef Workstation?
The latest version of Chef Workstation is 25.12.1102, released in the 25 release cycle.
How many versions of Chef Workstation are currently supported?
Chef Workstation currently has 2 actively supported version(s): 25, 24.
When does Chef Workstation 25 reach end of life?
Chef Workstation 25 does not have a specific end-of-life date announced yet.
What should I do when Chef Workstation reaches end of life?
When a Chef Workstation 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.