Chef Supermarket End of Life (EOL) Dates and End of Support (EOS) Dates
Chef Supermarket end of life (EOL) and end of support (EOS) dates: 3 Chef Supermarket versions have reached EOL, including Chef Supermarket 4 (EOL date: Mar 03, 2022) — no longer receiving security updates or patches. Chef Supermarket 5.3.7 is the current supported release. Also see RabbitMQ lifecycle dates for related end-of-life information.
Currently Supported Chef Supermarket Releases - Active EOS/EOSL Support (1)
| Release | Released | Security Support | Latest |
|---|---|---|---|
| 5 | (4 years and 8 months ago) | Active | 5.3.7 (3 months ago) |
Chef Supermarket End of Life (EOL) Releases - No Longer Supported (3)
| Release | Released | Security Support | Latest |
|---|---|---|---|
| 4 | (5 years and 1 month ago) | (4 years and 8 months ago) | 4.2.89 (4 years and 10 months ago) |
| 3 | (9 years and 7 months ago) | (5 years and 1 month ago) | 3.4.8 (5 years and 8 months ago) |
| 2 | (11 years and 3 months ago) | (9 years and 7 months ago) | 2.9.30 (9 years and 7 months ago) |
Wondering about Chef Supermarket end of life? Progress has marked Chef Supermarket 5.x as deprecated, with an EOL date of May 31, 2027, and points customers to the Chef 360 Platform. This announcement matters to anyone who hosts shared automation content internally, so here is what changes, when, and what to do about it.
Chef Supermarket end of life dates
The end-of-life schedule comes straight from Chef's lifecycle documentation. Supermarket 5.x moves to deprecated status on August 1, 2026, and reaches its final date on May 31, 2027. Chef notes that future dates can still shift, so check the documentation before you commit to a plan. Several neighbouring products on the Chef 360 path follow similar dates, and each product's own dates appear below.
| Product | Status | Deprecation date | Final date |
|---|---|---|---|
| Chef Supermarket 5.x | Retiring | August 1, 2026 | May 31, 2027 |
| Chef Infra Server 15.x | Retiring | Earlier | November 30, 2026 |
| Chef Automate (latest) | Generally available | November 1, 2026 | November 30, 2027 |
| Chef Infra Client 18.x | Retiring | Earlier | August 31, 2027 |
Organizations running a self-managed server should read the supported versions list closely, because the same table also covers every other deprecated release.
Deprecated versus retired releases in the product lifecycle
Chef describes each stage of the product lifecycle in plain terms, and the difference matters for your risk planning. Under the support rules, service-level agreements keep applying while a product is deprecated, but scheduled releases stop and a fix ships only for a critical defect. After the final date, nothing is promised and maintenance ends.
Generally available releases
These versions are in active development and receive regular updates; Supermarket 5.x held this stage until August 1, 2026.
Winding-down releases
These still get support, but no routine updates, as the deprecated label signals; Supermarket 5.x sits here from August 1, 2026 until May 31, 2027.
Retired releases
These are unsupported, and Chef no longer recommends them for production. After May 31, 2027, Supermarket 5.x falls into this stage.
Chef Marketplace, the successor to Chef Supermarket
Progress plans Chef Marketplace as the successor to Chef Supermarket. Its first release focuses on discovering and consuming public cookbooks, while later phases may add InSpec profiles and Habitat packages, though that wider scope is not confirmed. The vendor positions it as a safer, more modern home for reusable automation content on its platform. If you rely on community cookbooks, watch the announcement channels for the launch date and any import steps.
Deprecation impact on self-hosted installs
The Chef Supermarket cut-off hits self-hosted installs hardest, since fixes stop after May 31, 2027. Supermarket is an artifact store that serves internal and public content during Policyfile and Berkshelf depsolving, so a stale copy can quietly stop your builds from getting patches. Chef has long applied bug and security fixes to the latest release only, with no backported fixes for older majors. That makes it urgent to confirm which build you run:
- Run
supermarket-ctl versionon the server. - Compare it with the latest release, currently 5.3.7.
- Treat anything older as lacking security fixes, which is a real security gap.
Deprecated Chef Infra Server and Chef Automate timelines
Supermarket is not alone. Chef Infra Server 15.x reaches its EOL on November 30, 2026, and Chef Automate follows a year later. Progress names the Chef 360 Platform as the replacement product for both, while Chef Infra Client, Chef InSpec, Chef Habitat and Chef Workstation simply have newer versions to adopt. Platform teams running DevOps pipelines and infrastructure automation should list every Chef component they run.
Replacement and migration paths after the cut-off
For Supermarket itself, use the new marketplace for public content, or mirror what you need internally. For the wider platform you have three honest replacement routes, each with its own migration cost:
- Stay with Progress. Move to the Chef 360 Platform, accepting a single-vendor setup and a paid licence.
- Keep the open-source code. Cheap, but you absorb unpatched CVE exposure and every dependency update yourself, a bridge at best.
- Change tools. Teams often migrate to Ansible for configuration management, sharing roles through Ansible's own content hub instead of Supermarket.
For hosted users, Hosted Chef already ended: Hosted Chef customers were told to move to Chef SaaS, and Chef SaaS handles setup for them. Favour open-source foundations with commercial support, compliance evidence for auditors, plus shared infrastructure controls, and long-term support (LTS) versions, since unfixed vulnerability reports in a production tool are the risk to avoid.
Preparing your upgrade or transition before the cut-off
Start now: find every Supermarket install with supermarket-ctl version, list the content your teams pull from it, and note the May 31, 2027 EOL. Then test that content against the Chef 360 Platform and map dependencies. Whether the move is a version bump or a full transition to another platform, an upgrade or transition done early is calmer than one forced by the deadline. Check Chef's documentation for the latest dates.